Access displays #DELETED when you insert data with the same value into a non-unique Key column of a remote table
This article was previously published under Q291546
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 2000 version of this article, see 257487
When you try to add records to a linked SQL Server table, Access displays #DELETED when you commit the record. However, no error is returned, and the data is correctly saved to the table.
When you try to add records to a linked SQL Server table that includes a primary key that has a data type of UniqueIdentifier, #DELETED may be displayed when you commit the record.
Obtain the latest Microsoft Jet 4.0 service pack that contains an updated version of the Microsoft Jet 4.0 database engine.
For additional information about how to obtain the latest version of the Jet 4.0 database engine, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
This is a known issue in Microsoft Jet version 4.0.2927.4 and earlier.
Steps to Reproduce the Behavior
- Create a table in the Pubs sample database of Microsoft SQL Server 7.0 by running the following script in the SQL Server Query Analyzer:
Use PubsCREATE TABLE Table1 (col1 uniqueidentifier DEFAULT NewID() PRIMARY KEY NOT NULL, col2 int)go
- Create a new Access database, and then add a link to the SQL Server table that you created in Step 1.
- Open the linked table in Datasheet view.
- Add a record, and then in col2, type 123.
- Add a second record, and then in col2, type the same value, 123.
- On the Records menu, click Save Record.
Note that Access displays #DELETED in both fields of the second record.
pra attached pound number sign
Article ID: 291546 - Last Review: 08/11/2004 22:07:00 - Revision: 5.0
- Microsoft Access 2002 Standard Edition
- kbtable kbprb kbdisplay KB291546