Lock files not releasing

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RipperT - 14 Oct 2006 02:25 GMT

I hope I have the right group for this question. I have a Access 2000 split,
secured DB that refuses to let me into a table in design mode. Upon opening
the back end in exclusive mode, I get the error message: "You can't open
'G:\ITS\ITS_BE.mdb' for exclusive use because another user has the database
open or because you do not have permissions to open exclusively." I am the
DB admin and only I have permissions to open it exclusively. I can't say
that no one else has the front end open, but I do know that if any users are
logged into it, it is only thru the front end. Is this considered having the
database 'open'? If I open the back end in read only, then open the table in
design mode (only one table is offending, the rest are fine), Access tells
me: "You can't open 'tblInmates' for modification. A query or form bound to
the table is open, you may not have permission to open this table in design
view, or another user has the table open." It goes on to tell me to close
the bound query or form or I can open it in read only. If I have the back
end open in read only and I try the compact and repair utility, I get this:
"You attempted to open a database that is already opened exclusively by user
'SmithSP' on machine "XJD8D7'. Try again when the database is available."
I'm SmithSP! I don't get it. Interestingly, I cannot delete the lock files
or the back end from the server. Error messages saying they are being used.
This has only happened once in the DB's 2 year existence and rebooting the
server was the only way to release the lock files. In this case, I am
certain that no one else is logged in. To make sure, I had out network admin
reboot the server, and that fixed it. But after I opened the table
exclusively and made some changes to the offending table, I closed it and
went to work on the front end, then went back to the back end and, same old
problem. I am wondering if there is corruption in the back end, maybe just
in that one table? I don't pretend to understand the whole lock file deal, I
just know that I've never had trouble opening the back end whenever I wanted
and doing design changes. Sorry for the longwinded description. I hope
someone can help.

Reply to this Message

Larry Linson - 14 Oct 2006 03:07 GMT

If someone else has the database open in shared mode, you cannot open it
exclusively. And, any one of the users who has their front end database
open, with tables linked to the back end, has the back end "open."

And, there are times and circumstances where the MDW entry does not get
cleared when you exit... more likely if you are testing and it "blows up" or
if the network connection is dropped.

If I recall correctly, there are utilities that will allow deleting a file
even though it is open. You'd need to talk to your system administrator or
ask in a newsgroup about the OS that you are using for details, though.

Larry Linson
Microsoft Access MVP

>I hope I have the right group for this question. I have a Access 2000
>split, secured DB that refuses to let me into a table in design mode. Upon
[quoted text clipped - 26 lines]
>never had trouble opening the back end whenever I wanted and doing design
>changes. Sorry for the longwinded description. I hope someone can help.

Reply to this Message

RipperT - 14 Oct 2006 20:39 GMT

Thanks for your input, Larry. Even tho it's inconvenient, out admin has a
agreed to another server shutdown. What's your opinion on what to do while
it's down? Do you think using compact and repair on the back end will solve
the problem? My last known good backup is a week old. I'll I have alot of
catching up to do if I have to restore from that.

Many thanx,

Rip

> If someone else has the database open in shared mode, you cannot open it
> exclusively. And, any one of the users who has their front end database
[quoted text clipped - 42 lines]
>>whenever I wanted and doing design changes. Sorry for the longwinded
>>description. I hope someone can help.

Reply to this Message

Larry Linson - 15 Oct 2006 04:51 GMT

> Thanks for your input, Larry. Even tho it's
> inconvenient, out admin has agreed to another
[quoted text clipped - 4 lines]
> week old. I'll I have alot of catching up to do
> if I have to restore from that.

Make a copy, then Compact and Repair. It's always a good idea to compact
the backend DB on a regular basis. I don't know, but it doesn't seem
likely, that would cause the lock file problems.

Create a new, empty database. Use File | GetExternalData to import all the
Tables and Data from your back end.

Make certain that you have all the SPs for Access 2000 on all users'
machines, as well as all the SPs for the Jet 4.0 database engine (I think
there have been eight, but there may have been more.)

Just as a double-check, make certain you have file delete authorization for
the folder in which the back-end and LDB file reside.

Searching the KnowledgeBase at http://support.microsoft.com for Access 2000
and all the words "LDB not deleting" returned some articles that might be
helpful. MVP Tony Toews has a lot of good information on Access in the
multiuser environment.

Larry Linson
Microsoft Access MVP

Reply to this Message

david@epsomdotcomdotau - 29 Oct 2006 12:34 GMT

You shouldn't need to do a server shutdown! All you need is
to disconnect the 'user' from the lock file and the database file.
Any good network admin should be able to do that with his eyes
closed: any average to amateur admin should be able to find it
without too much difficulty. To make it easy for him, you have
to tell him the name and location of the database file and lock
file: if he's got a lot of users, they may have hundreds of different
files open.

> Thanks for your input, Larry. Even tho it's inconvenient, out admin has a
> agreed to another server shutdown. What's your opinion on what to do while
[quoted text clipped - 52 lines]
> >>whenever I wanted and doing design changes. Sorry for the longwinded
> >>description. I hope someone can help.

Reply to this Message