ACC1x: Referential Integrity Error Message with Shared Databases

• Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you share databases in Microsoft Access and try to update a record that another user has already updated, your update fails and Microsoft Access generates the following message:

   Data has changed; Operation stopped.

   This record has been changed by another user since you started
   editing it. If you save the record, you will overwrite the
   changes the other user made.

• Save Record
• Copy To Clipboard
• Drop Changes

   Can't delete or change record. Since related records exist in table
   "<Table Name>", referential integrity rules would be violated.

CAUSE

Your table is on the "one" side of a one-to-many relationship and the Enforce Referential Integrity check box is selected. These symptoms occur regardless of the field being edited.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0 and 1.1. This problem no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

Steps to Reproduce Behavior

1. Open two instances of Microsoft Access. In each instance, open the sample database NWIND.MDB. Make sure that the database is not opened with exclusive access.

2. In each instance, open the Categories table.

3. In the first instance, change the Category Name field in the first record. Do not commit the change.

4. In the second instance, change the Category Name field in the first record. Commit the change by moving the indicator to a field in another record.

5. Restore the first instance and try to commit the change. Microsoft Access generates the first of the two error messages listed above. When the second error message appears, choose Copy To Clipboard.

6. Select the first record from the first instance of Microsoft Access. From the Edit menu, choose Paste.

7. Try to close the table. Microsoft Access generates the referential integrity error message listed above.