[dba-SQLServer] Write Conflict Error - Access and SQL

[Susan Harkins]

I've read about his problem before, but I don't actually have a solution or
hint for you, but perhaps this will help: 

<
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ce92437b-da89-47d9-
9bbf-38a84b74ee62/receiving-write-conflict-error-when-trying-to-update-linke
d-sql-server-table-that-contains-a?forum=accessdev>



Susan H. 


Hi Listers,

 

I have a client with an SQL database in SQL 2014 with an Access accde front
end running in Access 2016.

 

A form uses an ADODB.Recordset assigned to the forms Recordset property to
get the records for the form.

 

The user can change a record and save it ok the first time but if they try
to change the same record again without refreshing the data they get a Write
Conflict error "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."

 

The table for the records contains a timestamp data type field, and doesn't
have any bit fields (these are the two main suggestions from other posts I
have found).

 

I have used the same Access database in Access 2010 with SQL2008 and it
doesn't cause the error.

 

Where should I start looking to work out why the form works on one
configuration but not the other?

 

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

 

 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com