Article ID: 280730 - View products that this article applies to.
This article was previously published under Q280730
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 97 version of this article, see 278696
You receive the following write conflict error when you try to update records in a linked SQL Server table:
You are then given the following options: Save Record, Copy to Clipboard, or Drop Changes.
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.
Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make changes.
Access is creating Null bit fields, which causes a type mismatch.
The linked table is using fields defined as floating point data type (i.e. Real). This data type allows for storing "floating point" number data. When the edited record is passed to SQL Server, if both engines see the data in these fields as having the identical value, there is no problem. However, because of the "rounding" algorithms used by JET and SQL Server, the actual value compared may be different. Since JET has to review each field and see if there are any concurrency issues, when JET compares the number it sees (in the "Real" data type field) to that value stored in SQL Server, if it does not match exactly the record is assumed to have been changed and a Write Conflict occurs.
To resolve the problem with bit data type, do one of the following:
To resolve the problem with floating point data types, do one of the following:
Steps to Reproduce BehaviorThe following steps assume that you have an understanding of how to create tables in SQL Server, and that you are familiar with certain SQL Server tools such as Enterprise Manager.
Also assumed is that you are aware of how to create File, User, and System Data Source Names (DSN), and how to use a DSN to link a table to a Microsoft Access 2000 database.
Article ID: 280730 - Last Review: July 29, 2004 - Revision: 2.1