Hi, Jessica.
them are "Full data users) the same record. I have just using
Tools -> Options -> Advanced and select "Default record locking" as "Edited
record". Is this step is enough to protect the write conflicting on the
shared DB?
It's a start, but there are a few more steps to take in order to reduce the
likelihood of record locks in a multiuser environment. Check the following:
1.) Is the database split into a front end and back end? The back end
contains the tables and relationships and is placed on the network server.
The front end contains the forms, queries, modules, et cetera, and a copy of
this file resides on each user's workstation.
2.) Is every database file (including the copies on each user's
workstation) set to "Open databases using record-level locking" on the
"Advanced" tab, as well? If the first user opens the database without this
set, then the database will be opened using page-level locking and all
others who open the database afterwards get the same setting as the first,
regardless of what their own setting is. If you are using Access 97, then
you won't get to make a choice. It's page-level locking only.
3.) Is every user's workstation and the server updated with the latest
service packs? You didn't mention which version of Access you are using,
but if it's Access 2K or later, then Jet 4.0 SP-8 and MDAC 2.8 SP-1 are two
of the three latest updates you need. If it's not possible to update
everyone to the latest, at least have everyone using the same version of Jet
and MDAC.
And you will probably have fewer write locks with "optimistic" locking
(select "No Locks" instead of "Edited Record"), but YMMV. As a suggestion,
create a button on the form that the user can use to requery the recordset
and return to the same record. The user will get the latest changes in the
database to make the next edit attempt to whenever a write lock occurs and
the user's first edit is tossed out.
And it depends upon your database design, but you may be able to re-design
it so that people are seldom editing the same record or adjacent records in
the tables, thereby diminishing the likelihood of write locks in the first
place.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
