Write Conflict in Access with SQL server Tables

[RW]

I have a write conflict as described by several others when trying to update
or add new information into forms or tables in an access database linked to
SQL Server tables through an ODBC connection. The problem happens after I
have changed the tables through SQL Server Enterprise manager and then go
back to working through Access. I have refreshed the tables in SQL Server,
deleted and re-linked the Tables in Access and have even made a new ODBC
connection and again re-linked the Tables.
Any suggestions?

RW

 

[Sylvain Lafontaine]

Some type of fields will give you trouble with the optimistic locking
mecanism of Access (bit field, BIGINT, some of out range decimal precision,
float, etc.).

Try replacing these types with something else or add a timestamp field to
your table(s).

 

[RW]

Some type of fields will give you trouble with the optimistic locking
mecanism of Access (bit field, BIGINT, some of out range decimal precision,
float, etc.).

Try replacing these types with something else or add a timestamp field to
your table(s).

Sorry for not getting back sooner, but I did not return to that client till
recently. I added timestamp fields to the Tables that were giving me problems
and the Write Conflict disappeared. Many thanks as the solutions I was trying
were time consuming and sometimes awkward.

 

[Sylvain Lafontaine]

Using the timestamp field will solve many problems with the optimistic
locking of Access; however, it cannot solve all and sometimes can be itself
the source of trouble (for example with some update or insert triggers).

You should take time to study the optimistic locking of Access and to use
the SQL-Server Profiler in order to better understand what's going on in
your case.