Runtime error -file sharing lock count exceeded

[Janis]

There is a split frontend backend database. Both files are on the z drive.
The front end is not on the users desktops. They have a shortcut to the
front end on the z drive. This was a security measure to keep the user from
messing up the front end file so all she has on her desktop is the shortcut.

In any case when running a report from the users desktop we get this error.
When I run the report directly accessing the ascs.mdb file it works fine.
The error is" run time error , "File sharing lock count exceeded. Increase
max Locks per file registry entry".

Am I supposed to edit the registry on the users computer? There is
something in the Knowledge Base that talks about synchronizing two replicas
in Access 2000. It is an Access 2000 db upgraded from 1997. What are they
talking about replicas?
thanks,

 

[golfinray]

You are eventually want to put either the FE or runtime on the user's
machines. You will not have near the locking problems if you do. You can make
it where the users only see the files they are supposed to work with.
Meanwhile, make sure that users have read/write/edit/and delete rights to the
BE file AND the folder it resides in. Go into tools\options\advanced and make
sure there are no locks engaged. I would also create a form with one item in
it and set it to open when your switchboard or mainform opens. That way when
you bring the database up you control the lock (ldb) file.

 

[Jerry Whittle]

Here's what you need to know. Yes you will need to mess with the registry.

http://support.microsoft.com/kb/815281

Don't worry about replication. I don't think it has anything to do with your
situation.

You should rethink putting the FE on the user's computer. You'll get much
better performance, plus there's nothing to stop them from messing with the
FE out on the server now. You could convert the FE to an MDE file and then
they couldn't mess with much of it. Even if they do mess with it, you could
just put a fresh copy of the FE on their computer.

 

[John W. Vinson]

There is a split frontend backend database. Both files are on the z drive.
The front end is not on the users desktops. They have a shortcut to the
front end on the z drive. This was a security measure to keep the user from
messing up the front end file so all she has on her desktop is the shortcut.

BAD idea. Sorry, but a shared frontend in a split database gives you the WORST
possible combination: none of the advanatages of a split database (you're
still needing to connect over the network), and all of the disadvantages of a
shared database (contention, corruption, and bad performance).

Just give the user their own copy of the frontend. If she messes it up,
overwrite it with a clean copy.

In any case when running a report from the users desktop we get this error.
When I run the report directly accessing the ascs.mdb file it works fine.
The error is" run time error , "File sharing lock count exceeded. Increase
max Locks per file registry entry".

Undoubtedly either contention between users, all trying to lock files from the
same frontend, or corruption.

Am I supposed to edit the registry on the users computer? There is
something in the Knowledge Base that talks about synchronizing two replicas
in Access 2000. It is an Access 2000 db upgraded from 1997. What are they
talking about replicas?
thanks,

Nope. Just do the split right and this won't happen.

 

[John W. Vinson]

plus there's nothing to stop them from messing with the
FE out on the server now

.... which messes it up for EVERYONE, not just for that one user.

 

[aaron.kempf]

wow dude.. what a pain in the ass.

you know, if you just upsized to SQL Server (and ADP!)-- so you could
enjoy this invention from the 80s called 'Client Server' then you
wouldn't have to worry about that crap

-Aaron