Unable to delete LDB File

[Sailor1877 via AccessMonster.com]

I've been reading all the threads about problems with LDB files but my
specific problem doesn't seem to be addressed. I have a back end database on
a server that I'm unable to run Compact and Repair on because the LDB file is
still present. It tells me it is being used by a user "Admin" on my machine
(a fact that is echoed when I open the LDB file in Notepad.) Unfortunately
there is no username "Admin" on the network.

When I try to delete the LDB file I'm told that the file is in use. I have
Full Access rights on the folder where the DB is kept.

Any suggestions short of rebooting the file server?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1

[Rick Brandt]

Sailor1877 via AccessMonster.com wrote:

I've been reading all the threads about problems with LDB files but my
specific problem doesn't seem to be addressed. I have a back end
database on a server that I'm unable to run Compact and Repair on
because the LDB file is still present. It tells me it is being used
by a user "Admin" on my machine (a fact that is echoed when I open
the LDB file in Notepad.) Unfortunately there is no username "Admin"
on the network.

When I try to delete the LDB file I'm told that the file is in use.
I have Full Access rights on the folder where the DB is kept.

Any suggestions short of rebooting the file server?

If you are in the front end and any bound objects are opened then you are
also IN the back end and "Admin" is YOU. You won;lt be able to compact the
back end form thje fron enbd unless you make sure that there are no open
connections to the back end. Then the LDB will be deleted automatically.

In this context "Admin" is the Access user name, not a network or windows
user name. If your file does not utilise User Level Security then everyone
who opens the file is identified as "Admin".

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Sailor1877 via AccessMonster.com]

Thanks, but when this happens I am in the back end file and the front end is
not open. I've had my computer completely shut down and logged in as
administrator (not my usual log in) on other computers but the LDB file is
still there and I still can't delete it or run Compact.

Rick Brandt wrote:

>I've been reading all the threads about problems with LDB files but my
specific problem doesn't seem to be addressed. I have a back end

[quoted text clipped - 8 lines]

>>
Any suggestions short of rebooting the file server?

If you are in the front end and any bound objects are opened then you are
also IN the back end and "Admin" is YOU. You won;lt be able to compact the
back end form thje fron enbd unless you make sure that there are no open
connections to the back end. Then the LDB will be deleted automatically.

In this context "Admin" is the Access user name, not a network or windows
user name. If your file does not utilise User Level Security then everyone
who opens the file is identified as "Admin".

--
Message posted via http://www.accessmonster.com

[David W. Fenton]

"Rick Brandt" <ri*********@hotmail.comwrote in
news:QM*****************@newssvr11.news.prodigy.co m:

Sailor1877 via AccessMonster.com wrote:

>I've been reading all the threads about problems with LDB files
but my specific problem doesn't seem to be addressed. I have a
back end database on a server that I'm unable to run Compact and
Repair on because the LDB file is still present. It tells me it
is being used by a user "Admin" on my machine (a fact that is
echoed when I open the LDB file in Notepad.) Unfortunately there
is no username "Admin" on the network.

When I try to delete the LDB file I'm told that the file is in
use. I have Full Access rights on the folder where the DB is
kept.

Any suggestions short of rebooting the file server?

If you are in the front end and any bound objects are opened then
you are also IN the back end and "Admin" is YOU. You won;lt be
able to compact the back end form thje fron enbd unless you make
sure that there are no open connections to the back end. Then the
LDB will be deleted automatically.

In this context "Admin" is the Access user name, not a network or
windows user name. If your file does not utilise User Level
Security then everyone who opens the file is identified as
"Admin".

Sometimes the LDB file gets corrupted or has a file lock held open
and it won't delete.

There are two things to do:

1. first reboot your workstation. This should release any open file
handles on the server.

2. failing #1, then use the server administration tools to force
close the file.

Once that's done, you should be able to delete the LDB file.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Sailor1877 via AccessMonster.com]

Forcing the file closed did the trick.

Thank you. Both.

David W. Fenton wrote:

>>I've been reading all the threads about problems with LDB files
but my specific problem doesn't seem to be addressed. I have a

[quoted text clipped - 20 lines]

>Security then everyone who opens the file is identified as
"Admin".

Sometimes the LDB file gets corrupted or has a file lock held open
and it won't delete.

There are two things to do:

1. first reboot your workstation. This should release any open file
handles on the server.

2. failing #1, then use the server administration tools to force
close the file.

Once that's done, you should be able to delete the LDB file.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1