Article ID: 182867
Article Last Modified on 1/22/2007
This error typically occurs when a long value column (an OLE or MEMO data-type) has bad data stored in it. Long value columns are typically stored in a separate page from the page that the row is stored in. If a long value column is present in the table schema, the Jet database engine will attempt to read the long value page when reading the row of data. In order to read the long value page, there is a pointer in the row of data. This error is generated when the Jet database engine cannot properly read the long value page from the pointer present in the data row. When viewing a row that exhibits this behavior in Microsoft Access data-windows, the user will typically see the number sign (#) for the entire row.
This is typically caused when the Jet database engine was improperly shut down during the process of writing to disk.
This error message is typically caused when there is an index missing on the MSysObjects table. This is typically caused if the repair process is aborted.
172733 ACC97: Updated Version of Microsoft Jet 3.5 Available for Download
Jet35SP3.doc
109953 ACC: How to Repair a Damaged Database
Additional query words: jet 3 x isn t
Keywords: kberrmsg kbinfo KB182867