...a state that prevents it from being opened or locked...

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mikelee101@hotmail.com - 24 May 2006 19:05 GMT

Hello,
We have a database on a network drive used by 6 people. At the moment,
when anyone tries to open it, they receive the error message:

"The database has been placed in a state by 'Admin' on machine
'<computername>' that prevents it from being opened or locked."

Here's the quandry. The person who works on the computer named in the
error message is at lunch, and the PC is locked.

My question...can I open the .ldb in Notepad and delete the machine
name? Would that allow other users to open the database? Would that
cause any issues for her when she got back?

If opening it in Notepad wouldn't work, I've seen some posts which
mention an application called LDB Viewer. Would this work and where
should I get it?

Or is there another way to allow people to open the database without
messing with the ldb?

Thanks to all for the help.

Mike Lee
Coppell, TX

Reply to this Message

Douglas J. Steele - 24 May 2006 22:57 GMT

I wouldn't recommend it. Since the user still has a connection open to the
database, you could end up corrupting the database.

Why not use a technique like in http://support.microsoft.com/?id=128814 to
log the user off after a certain amount of inactivity?

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

> Hello,
> We have a database on a network drive used by 6 people. At the moment,
[quoted text clipped - 21 lines]
> Mike Lee
> Coppell, TX

Reply to this Message

mikelee101@hotmail.com - 25 May 2006 21:11 GMT

Doug,
Great idea. Thanks for the help.

Mike

Reply to this Message

JohnC - 08 Jun 2006 03:17 GMT

Have you checked that this user has Adobe Acrobat or Adobe Professional 7.0
or later (not the reader). This version of Adobe installs by default the
PDFMaker in all MS Office applications. The PDFMaker creates a toolbar and
in a shared application such as Access, you get the error as you mentioned.
The PDFMaker really isn't necessary in Access because the user can still
print to the Adobe printer to create the .pdf file.

Easy fix,
In Add/Remove Programs, Adobe Acrobat (or Professional), Change, expand
Create PDF, expand PDFMaker, and select "do not run from computer" for
Access.

John

> Hello,
> We have a database on a network drive used by 6 people. At the moment,
[quoted text clipped - 21 lines]
> Mike Lee
> Coppell, TX

Reply to this Message

Mark Burns - 26 Jun 2006 19:55 GMT

John,

Do you have a source for this information?
We were experiencing the same exact issue, and your tip seems to be
resolving this, but I'll be darned if I can find _anything_ about this via
Google or any other search tools...(even the search of all the MSDN Access
newsgroups only turned up your post!)

> Have you checked that this user has Adobe Acrobat or Adobe Professional 7.0
> or later (not the reader). This version of Adobe installs by default the
[quoted text clipped - 35 lines]
> > Mike Lee
> > Coppell, TX

Reply to this Message

david epsom dot com dot au - 02 Jul 2006 12:07 GMT

To find related information in google groups, search for

toolbar exclusive group:*access*

(david)

> John,
>
[quoted text clipped - 46 lines]
>> > Mike Lee
>> > Coppell, TX

Reply to this Message