I have "Write Conflict" error on linked table to sql server when I want to edit field value but, when I update value by using "Update Query", it is done successfully. How it is possible to edit value by query but it is impossible directly in linked table. After executing update query, that error shown again. Why only with table?
New contributor
Hadi Mazareei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
-
The main reason of my question is why it is possible by query and impossible directly in table?Hadi Mazareei– Hadi Mazareei2025-10-24 04:54:14 +00:00Commented yesterday
Add a comment
|
1 Answer
This could be a null bits issue described in this very old article: KB280730 (last snapshot on Wayback Machine; the original article was deleted). If you are using bit fields, set their default value to 0 and replace any NULLs entered before by 0. I usually use a BIT DEFAULT 0 NOT NULL for Boolean fields as it most closely matches the idea of a Boolean.
The KB article says to use an *.adp file instead of a *.mdb file; however, Microsoft discontinued the support for Access Data Projects (ADP) in Access 2013.
Make sure the SQL Server table has a primary key as well as a timestamp (= rowversion) column.
The timestamp column helps Access to determine if the record has been edited since it was last selected. Access does this by inspecting all fields, if a timestamp is not available. Maybe this does not work well with null entries if there isn’t any timestamp column (because of the Null bits issue).
The timestamp actually stores a row version number and not a time.
Don't forget to refresh the table link in Access after adding a timestamp column; otherwise Access won't see it. (Note: Microsoft's Upsizing Wizard creates timestamp columns when converting Access tables to SQL Server tables.)
answered yesterday
