file with a lock

[Dooma]

I have a big access file (17MB) that when we try to open it, it will not
open but creates another file with .ldb extension and a lock on it. Any
ideas?

Thanks.

 

[Douglas J. Steele]

Define "will not open". Do you get any error message? Does Access open, but
there's no database window visible?

The fact that the locking file (.ldb) gets created makes me suspect that the
database has been set up not to display the database window upon startup,
but they forgot to set a startup form. You could try holding down the shift
key as you're opening the database, just in case they didn't disable
AllowBypassKey.

 

[Dooma]

It gives me a run time error in the ODBC. I am not really knowledgeable in
access. I hope these information are helpful.

 

[Douglas J. Steele]

I think you'd better provide more information.

It sounds as though you're not actually opening the database, but trying to
connect to it. How are you doing that? (post the relevant code here, please)
What's the exact error message you're getting?

 

[Guest]

hi,

i'm in a similar situation.....let me explain:

i have an a2k file on a network ("I") shared drive called "EXPERIMENTAL
Screening Log (10-28-04)a.mdb" (5328 kb) which has a 'ldb' file called
EXPERIMENTAL Screening Log (10-28-04)a.ldb (0 kb) sitting alongside it.

i first encountered this problem yesterday around 3pm when i noticed that in
attempting to open the a2k file nothing happened: no error messages, no a2k
window, no....

when i next examined the file's directory i noted the existence of the 'ldb'
file.

i have encountered this kind of scenario (which gives me a ldb file that can
not be deleted manually or automatically for hours at a time) prevously.
what i usually do is make a copy of the mdb file and paste it back onto the
computer and go from there. usually, but not this time, when i return the
next date the 'ldb' file has disappeared 'on its own' .

when i arrived this am, the 'ldb' file was still around so i figured it was
time to hit the discussion group.

anybody?

 

[Douglas J. Steele]

If Access was terminated inappropriately, it's possible that the thread
won't have released the LDB file, meaning that you can't delete it.
Rebooting the server will usually solve the problem, although that's
admittedly a little drastic to have to do each time. Presumably the user who
had the problem logging off will release the thread as well.

 

[Guest]

i believe the user to 'cause' the issue is none other than yours truly.
failing a call to the network folks with this suggestion, how would i explore
the secondary idea to do with 'releasing the thread' (foreign concept at this
time).

best regards,

ted

 

[Douglas J. Steele]

Try logging off the network, then back on. In fact, try rebooting your
workstation. That should terminate any connections you still have to the
server, so that you won't be holding the LDB file open in any way.

 

[Guest]

rebooting this worked like a charm.

you're the man douglas j. steele

thanks!

ted

 

[Pieter Wijnen]

there are also some Win2K issues regarding Opportunistic locking involved
which can be turned off to help this kind off problems
search th mskb on "Opportunistic locking"
the way to toggle it is found in
http://support.microsoft.com/default.aspx?scid=kb;en-us;296264

HTH

Pieter