ACC2000: Table Corruption After Referential Integrity Checks (296389)
The information in this article applies to:
This article was previously published under Q296389 Novice: Requires knowledge of the user interface on single-user computers.
This article applies only to a Microsoft Access database (.mdb).
SYMPTOMS
When you are running an append query, you receive the following error message:
Microsoft Access can't append all the records in the append query.
Microsoft Access set 0 field(s) to Null due to a type conversion failure, and it didn't add <number> record(s) to the table due to key violations, 0 record(s) due to lock violations, and 0 record(s) due to validation rule violations.
Do you want to run the action query anyway?
To ignore the error(s) and run the query, click Yes.
For an explanation of the causes of the violations, click Help.
-or-
If you try to export a table, you receive the following error message:
The Microsoft Jet Database Engine could not find the Object ". Make sure the object exists and that you spelled its name correctly.
After clicking OK to the error message, you receive the following error message:
An error occurred trying to export the data from table 'tablename'. The data was not exported.
-or-
If you try to compact a database you, receive the following error message:
"Could not find field "Description"
CAUSE
You may experience this behavior with a table that has a self-join and Memo fields, and has referential integrity enforced.
RESOLUTION
To resolve this issue, change the Memo fields to Text fields or move the Memo fields into a separate table, and then use a 1:1 relationship.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 6/25/2004 |
|---|
| Keywords: | kbbug kberrmsg kbnofix KB296389 |
|---|
|