The first question is how you have your database structure. There are two
common structures:

1. A single MDB out on a network drive that everybody uses. This is a REAL
bad idea because a single instance of an MDB uses all sorts of internal
tables that are not necessarily sharable. Trying to have two or more people
use the same executable will often give this error.

2. Two MDBs -- one that contains only the data tables and resides on the
network drive (which I'll refer to as the data database). The second (which
I'll refer to as the program database) that contains only the programs,
queries, modules, macros, and reports as well as links to the data tables on
the network drive. Each user would have his/her own copy of the program
database running on his/her own local workstation.

If you have the second structure, that's a good start. Then we have to
worry about a few other things:

1. Type of locking in the forms and code. The default for Access forms is
"optimistic locking". If you're using any other kind of locking, it could
be that a users are stepping on each other because you have whole tables
locked.

2. The number of users. Since Access is not client-server, it moves a hell
of a lot of data across the network, and you can often get locking problems
because the sheer volume overwhelms the speed of the network. How many
users do you have and how big are the tables? More to the point, does this
happen with only one user?

3. Is there a spurious lock file (.LDB) file floating around - especially
on the server. Get ALL users out of your system (including yourself) and
then use Windows Explorer to see if there is still a .ldb file on the
network drive that contains your data database). If there is, delete it.
This can happen sometimes when a program fails in testing.

4. This kind of problem could come about if your linking of the main and
subform for tblMaster and tblSub. I can't tell from what you've written if
there's a problem there.

Your best bet might be to test it with a single user (you). If you get the
problem, then it's probably your form/table design. If not, then it might
be type of locking or number of users.

It would be useful if you posted more about your tables and forms.


"Paul" wrote in message
...
I have a multiuser database based around 2 main tables -
TblMaster and TblSub. They are linked with a one
(TblMaster) to many (TblSub) relationship. Now, when
someone enters data into the TblMaster fields and then
tries to enter any data, either from a combo box or into a
blank field, into the subform the database freezes and
about 10 seconds later an error dialogue box pops up
saying "Could not update; currently locked".

Can anyone shed any light on what is causing this and how
to rectifiy it?

Thanks,