Why does my DB not allow any updates when 18 locks are reached?

[Guest]

I have an Access '03 Database that is located on a shared drive on a central
server. If too many people try to access the database at once, then nobody
can do anything until someone else closes the file. When I go into File
Manager on the server, I can see the number of locks placed on the file by
every person that has it open, and it's usually 6 locks per person, but
sometimes it jumps up to 11. I've noticed that if the total number of locks
goes over 18, then that's when the problems start. Is there any way that I
can increase the number of available locks? Or reduce the number of locks
that each person has? Thanks.

 

[Joseph Meehan]

I have an Access '03 Database that is located on a shared drive on a
central server. If too many people try to access the database at
once, then nobody can do anything until someone else closes the file.
When I go into File Manager on the server, I can see the number of
locks placed on the file by every person that has it open, and it's
usually 6 locks per person, but sometimes it jumps up to 11. I've
noticed that if the total number of locks goes over 18, then that's
when the problems start. Is there any way that I can increase the
number of available locks? Or reduce the number of locks that each
person has? Thanks.

It sounds like they are all accessing the same file directly.

Try splitting the database file into one back end file and a front end
file, with a copy of that front end file on each users machine. The back
end houses the tables and the front end has all the rest. I suspect that
will eliminate your problem and prevent other problems you have not yet
discovered.

 

[Guest]

I just split the file, we'll see what happens on Monday, but I can already
see a vast difference in the number of locks. Thanks!!