ACC97: Write Conflict Error When You Try to Update Records in a Linked SQL Server Table (278696)
The information in this article applies to:
This article was previously published under Q278696 Advanced: Requires expert coding, interoperability, and multiuser skills.
For a Microsoft Access 2000 version of this article, see 280730.
SYMPTOMS
You receive the following write conflict error when you try to update records in a linked SQL Server table:
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.
You are then given the following options: Save Record, Copy to Clipboard, or Drop Changes.
CAUSE
Access is creating Null bit fields, which causes a type mismatch.
RESOLUTION
To resolve this problem, do one of the following:
- Using SQL Server, open the table in Design view, and assign a default value of 0 (that is, zero) on all bit fields.
NOTE: With this option, you must update records entered before this change was made. See the next item for more information.
- Using SQL Server, run an Update Transact-SQL statement against the table, and set all bit fields that have a value of Null to a new value of 0 or 1.
- Using SQL Server, change the bit fields to some other data type, such as int or tinyint.
- Using SQL Server, add a timestamp field to the table.
Modification Type: | Major | Last Reviewed: | 10/20/2003 |
---|
Keywords: | kbprb KB278696 |
---|
|