Locking Error? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Locking Error?

We are using Access as a front end for out people in the office. It select’s records from sql server brings them in for updated/viewing… Randomly we recieve this error thru Access. Write Conflict 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.
Then it has 3 buttons: the Save Record button is grayed out and not clickable…. Save Record Copy to Clipboard Drop Changes
Do all your tables have a PRIMARY KEY? —
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)

…and a TIMESTAMP column? —
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)

Not all the tables have primamry and/or imprtstamps
I have only limited Access exposure nowadays, but IIRC you need both in order to get it working properly. For the underlying reasons behind this, you better search the Google Archives of some Access newsgroup. This question pops up regularly there. Actually, that’s where I caught up this advise some time ago. [<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />]<br /><br />–<br />Frank Kalis<br />Microsoft SQL Server MVP<br /<a target="_blank" href=http://www.insidesql.de>http://www.insidesql.de</a><br />Ich unterstütze PASS Deutschland e.V. <a target="_blank" href=http://www.sqlpass.de>http://www.sqlpass.de</a>) <br />
If you want to do any kind of data entry from Access, you definitely must have a primary key defined. Not sure about the timestamp column, but it certainly can’t hurt to have one.
OK… thanks. I googled and found a good link. I LOVE YOU GOOGLE! http://support.microsoft.com/default.aspx?scid=kb;en-us;280730 thannks again.
]]>