Database locks for one user (tried all suggestions I found here)

[Melvis]

Hi,

I am trying to help redesign a database for another department in our
company. In the process of reverse-engineering their current database, I have
found out from users that one user locks them out of the database
consistently (1 or 2 times a week). I checked that user's default Open Mode
and it is Shared. I checked their read/write/delete permissions on the folder
and the files - all are there. Is there anything else this could possibly be?

Thanks in advance for your help...

 

[ChrisBat]

Hi Melvis,

Funny you should mention this - I have the same problem...the database is on
a shared drive, and for some reason, one person is consistently locking the
database. She double clicks the shortcut on her desktop, and it somehow lets
her have exclusive access. Really annoying, especially saying as she's a wee
bit of a snot, and gets really defensive when I ask her anything about the
database.
I'll watch this post and see what comes up.
Chris

 

[Melvis]

Guess either they think you answered my question or there is no other answer.
Mine is also on a network drive using a shortcut from the desktop...

 

[Joan Wild]

Guess either they think you answered my question or there is no other
answer. Mine is also on a network drive using a shortcut from the
desktop...

Another possibility is that the /excl switch is included in the shortcut
target.

Also check the folder permissions for *all* users, not just the one. They
need full permissions on the folder.

You should also split the mdb and have just the backend on the server. Give
each user a copy of the frontend on their computer.

 

[Melvis]

From what I understand, the database was split and set up the way you suggest
and they had problems so they just moved the front end to the same directory
as the backend. That is how it runs now...

 

[Melvis]

Ok - I just checked a few more things.
1. They are using Access 2002 SP2.
2. I can't check permissions for all users right now, but will ASAP
3. There is no / switch in the shortcut at all, just a path to the front end
file
4. There are not currently any subforms in the database
5. It is possible that they are the only ones with the database open
(referring to the problem discussed here
http://support.microsoft.com/default.aspx?scid=kb;en-us;247180), but that is
only supposed to effect Access 2000. Would this also effect an Access 2000
database in Access 2002???

 

[Joan Wild]

From what I understand, the database was split and set up the way you
suggest and they had problems so they just moved the front end to the
same directory as the backend. That is how it runs now...

That is not recommended. Each user should have their own copy of the
frontend.

What problems did they have?

 

[Joan Wild]

Ok - I just checked a few more things.
1. They are using Access 2002 SP2.
2. I can't check permissions for all users right now, but will ASAP
3. There is no / switch in the shortcut at all, just a path to the
front end file
4. There are not currently any subforms in the database
5. It is possible that they are the only ones with the database open
(referring to the problem discussed here
http://support.microsoft.com/default.aspx?scid=kb;en-us;247180), but
that is only supposed to effect Access 2000. Would this also effect
an Access 2000 database in Access 2002???

I don't think so. Also ensure that all users are running the latest version
of Jet - it's up to SP8, and there was an additional security update for
Windows that installed a change to Jet.

If you run Windows Update you should be up to date, however you can check
their version of Jet. Find the msjet40.dll file, right-click and go to the
version tab - it will say 4.0.8618.0 if you are up to date.

You also mentioned that the database was set to Open shared - however check
the backend as well - this setting is stored in the database, not for Access
as a whole.

 

[Melvis]

Probably something along the same lines as the problems they are having now.
The database I redesigned for them has seperate front-ends and they will get
installed locally. I just don't want this database locking problem when I
install the new one...

Both databases (front- and back-end) are set to open shared...

I will be checking the permissions and Jet version for each user tomorrow
morning. Thanks for the tips!

~MATT