I have found a frustrating write conflict error while building MS Access forms with linked SQL Server tables.
There are issues with not having a Timestamp (RowVersion) field, but I finally stumbled across the culprit that was affected several forms. If there is a bit field with null values, you can’t edit the record. You can add a new record, but if you edit the record and close the form, or go to the next record, you will be asked to cancel the change or copy to clipboard.
The error can also happen with floating point data types.
A simple fix to the bit field is to default the value to 1 or 0, or use a SmallInt field type instead of bit.