Implementing a good record locking strategy.

  • Thread starter Thread starter Atlas
  • Start date Start date
A

Atlas

I've developed a small client/server project with Access and SQL server
2000, where the duty has been performd mostly by bounded forms. Quite small
code updating.

What (I think) I've learned is that Access at it's best, when dealing in a
multiuser environment, can only check if a record changed in the backside
before updating.

Better than nothing, but what if we would like to plan something smarter?
Did anyone tried to stretch the product to it's limits, implementing a good
record locking strategy. If so, how, when and with what results?

Any online primer?

Bye
 
The best record locking strategy is not to use locks whenever
possible. Load data for browsing read-only, and load only single
records for editing. If you really want to support a lot of concurrent
users, then work with data "unbound", where forms are loaded with
disconnected data and all updates are posted back to the server via
stored procedures. This will require handling concurrency violations
yourself, and mandates a good database design to minimize conflicts.

-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
 
Back
Top