'Optimistic record locking' - what is it?
- Thread starter Carl_R
- Start date
Mile-O
Back once again...
- Local time
- Today, 12:33
- Joined
- Dec 10, 2002
- Messages
- 11,316
Optimistic locking: Where Access only tries to lock a record when someone tries to save any changes that they have made.
Optimistic locking implies that, when a user edits a record, Access optimistically assumes that noone else will want to edit the same record, and so it doesn't lock it.
Pessimistic locking: When Access locks a record whenever someone starts to change the contents of that record.
Pessimistic locking implies that, when a user edits a record, Access pessimistically assumes that someone else will want to edit the same record and so needs to lock it.
Optimistic locking implies that, when a user edits a record, Access optimistically assumes that noone else will want to edit the same record, and so it doesn't lock it.
Pessimistic locking: When Access locks a record whenever someone starts to change the contents of that record.
Pessimistic locking implies that, when a user edits a record, Access pessimistically assumes that someone else will want to edit the same record and so needs to lock it.
Thanks for the reply 
Is there a chance that with Optimistic locking, two users updating the same object can cause DB corruption?
Oh, and how does one turn off Optimistic locking? Can't seem to find anything in Access97 with any reference to this.
Is there a chance that with Optimistic locking, two users updating the same object can cause DB corruption?
Oh, and how does one turn off Optimistic locking? Can't seem to find anything in Access97 with any reference to this.
- Local time
- Today, 06:33
- Joined
- Feb 28, 2001
- Messages
- 30,019
There is always a chance that a single user on a stand-alone machine can cause database corruption. (Access IS, after all, a Microsoft product...)
The issues of corruption would occur with greater frequency if you have users sharing the database but don't have it set up with workgroups and normal file locking.
Corruption would also occur if the users had the wrong access rights on the directory in which the shared copy of Access resided. They have to be able to lock and unlock things.
To do it right, users must be able to create and delete files as well as read and write to them. (Specifically, the xxx.LDB file where xxx.MDB is your database file.) If the users cannot create the .LDB file then corruption becomes a significant possibility.
The issues of corruption would occur with greater frequency if you have users sharing the database but don't have it set up with workgroups and normal file locking.
Corruption would also occur if the users had the wrong access rights on the directory in which the shared copy of Access resided. They have to be able to lock and unlock things.
To do it right, users must be able to create and delete files as well as read and write to them. (Specifically, the xxx.LDB file where xxx.MDB is your database file.) If the users cannot create the .LDB file then corruption becomes a significant possibility.
Similar threads
