Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
ACC: Inconsistent Behavior with Multiple-Field Primary Key
Article ID: 170779 - View products that this article applies to.
This article was previously published under Q170779
Novice: Requires knowledge of the user interface on single-user computers.
In Microsoft Access version 7.0 or later, you may see inconsistent behavior when you define a relationship that enforces referential integrity, and the "one-side" table contains a multiple-field primary key. You can create a relationship, even though a record in the "many-side" table contains a Null value in one of the foreign key fields. However, after the relationship has been defined, you receive the following error message when you change another record in the "many-side" table so that it also contains a Null value in one of the foreign key fields:
You can't add or change a record because a related record is required in table <table>.
In Microsoft Access 7.0, you receive the message:
Can't add or change record. Referential integrity rules require a related record in <table.>
Microsoft has confirmed this to be a problem in the Microsoft Access versions listed at the beginning of this article. This problem no longer occurs in Microsoft Jet Database Engine version 3.51, which is available from the Microsoft Download Center.
For information on how to obtain Microsoft Jet Database Engine 3.51, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/172733/EN-US/ )ACC97: Updated Version of Microsoft Jet 3.5 Available for Download
Steps to Reproduce Behavior
For more information about referential integrity, ask the Microsoft Access 97 Office Assistant, or search the Help Index for "referential integrity" and select "What is referential integrity?"
Article ID: 170779 - Last Review: January 20, 2007 - Revision: 3.1