Hello Jerry,
You wrote in conference microsoft.public.access.adp.sqlserver on Mon, 7 Aug
2006 12:02:19 -0700:
JB> One of my developers tells me when using an Access ADP against a SQL
JB> Server 2000 back in there are concurrency issues. He has seen one user
JB> edit a record while another user has the same record open and then the
JB> second user can make changes and save the record without receiving any
JB> "the data has changed" prompts.
JB> Any ideas here?
Yes, it would work exactly like this. However, when the first user also
tries to save the record, he would receive the warning that the record was
already changed by someone else while he was working with it.
Access is using client-side cursors, so no locking occurs in the database
when the record is opened for edit. Whoever saves first, wins.
Server-side cursors and proper locking become an artifact of the past, and
not only in Access. All new database methods in newer languages like vb.net
are explicitly webserver-oriented, they all are using client-side cursors,
effectively looking at the database as a big excel table.
Vadim Rapp
|