What problems would arise if all forms have a "No locks"
I have an access 2000 database that is running in a multi-user environment, and all of the forms have a "No locks" in its properties.
Tools --> Options --> Advanced TAB
Default Record Locking
No locks
The above default is applied for all forms. All of the form properties is set to No locks.
//////////////////////////
Tools --> Options --> Advanced TAB
Open databases using record-level locking
//////////////////////////
Since none of the forms have any locks in the
record, would it causes problems such as
inaccurate query output when a user runs a query from a form (such as a button that activate a query) when multiple users may access the same record ?
What is the chief effect when all of the forms have a "No locks" in its properties and the the database is running in a multiuser environment ?
Tools --> Options --> Advanced TAB
Default Record Locking
No locks
The above default is applied for all forms. All of the form properties is set to No locks.
//////////////////////////
Tools --> Options --> Advanced TAB
Open databases using record-level locking
//////////////////////////
Since none of the forms have any locks in the
record, would it causes problems such as
inaccurate query output when a user runs a query from a form (such as a button that activate a query) when multiple users may access the same record ?
What is the chief effect when all of the forms have a "No locks" in its properties and the the database is running in a multiuser environment ?
Well, for one, your DB will run faster because Access will not do so much housekeeping. This is not advisable in multiuser environment because two users will be able to change a record at the same time without receiving a warning.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Pete, What's the difference then between no locks and edited record?
Its in the timing of the lock.
For edited record the record is locked as soon as editing begins and stays until the record has been saved. (So this leads to the proverbial 'gone to lunch' problem when the user walks away part way through the edit.)
For no locks the record is not locked until the moment of saving and the lock is released immediately the save is completed.
Pete
For edited record the record is locked as soon as editing begins and stays until the record has been saved. (So this leads to the proverbial 'gone to lunch' problem when the user walks away part way through the edit.)
For no locks the record is not locked until the moment of saving and the lock is released immediately the save is completed.
Pete