Effectively Handling Locking Conflicts
If a user has a page or record locked and another user tries to view data in the record or on that page, no conflict occurs. On the other hand, if other users try to edit data on that same page, they get an error.
You won't always want Access's own error handling to take over when a locking conflict occurs. For example, rather than having Access display its generic error message indicating that a record is locked, you might want to display your own message and then try to lock the record a couple of additional times. To do something like this, you must learn to interpret each locking error generated by VBA so that you can make a decision about how to respond.
Locking conflicts happen in the following situations: ...
Get Alison Balter's Mastering Access 2002 Enterprise Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.