"Access.LockFile.9" Help - can't open database

[Sandy]

Hello -

For some reason, all of a sudden I can't open my database again after I have
been in it for some time. I noticed the Access.LockFile.9.ldb is still in
with my regular .mdb file (although I have been able to open it in the past
with this present). The only way I can open the database is to reboot my
machine!!

Is this file corrupted or is there a setting I can change to stop this
behavior?

Any help will be greatly appreciated!

 

[TC]

What do you mean, you can not open it? Do you get an error message? If
so, what is the message?

TC

 

[Sandy]

Hi TC -

Thanks for your response. I mean, I click on it and there is nothing, nada
.. . . no error message, nothing. It just doesn't open, period.

Any thoughts on this?

 

[TC]

Can you open it by starting Access, then using File : Open from within
Access? If so, do that & then compact & repair, then try again.

HTH,
TC [MVP Access]

 

[Sandy]

Hi TC -

Thanks again for responding. I did try the File open thing and it didn't
open. As I said, the only way I could get it to open is to shut the computer
down. Is that Access.LockFile.9 supposed to stay for any length of time? Is
there a setting to make it go away faster?

Is that in fact what's interfering with it?

Again, any help is greatly appreciated!

 

[Michael Miller]

Hi Sandy,

There is a program called JETCOMP.EXE, which can do a compact and repair,
without you opening the database.

http://support.microsoft.com/default.aspx?scid=kb;en-us;273956

Read the instructions.

It supports up to the Access 2000 file structure, so if you're using a
higher version, keep checking.

I also have a JETCU40.EXE, but forgot what it was for. You might search for
it here on MSDN.

 

[Dirk Goldgar]

Hello -

For some reason, all of a sudden I can't open my database again after
I have been in it for some time. I noticed the Access.LockFile.9.ldb
is still in with my regular .mdb file (although I have been able to
open it in the past with this present). The only way I can open the
database is to reboot my machine!!

Is this file corrupted or is there a setting I can change to stop this
behavior?

Any help will be greatly appreciated!

I wonder if perhaps your database is still open even after you think
you've closed it, and the application window has been removed from the
screen. After you think you've closed it, and you have no other Access
applications open -- and the lock file still exists in the folder --
open the Task Manager and look through the list of running processes to
see if MSACCESS.EXE is still there. If it is, and you don't knowingly
have any Access application open, then try ending that task, and then
delete the lock file.

There are a couple of programming errors that can make Access fail to
close. If this is the problem, further investigation is required. What
version of Access are you using?

 

[Sandy]

Hi Michael -

Thanks for your response. For some reason, when I took it to work today, I
had no problem on it with that machine.

I copied the file and installed it at home tonight and so far, no trouble!
I did download JETCOMP.EXE and have it handy should I have the problem in the
future.

Thanks!

 

[Sandy]

Hi Dirk -

Thank you for responding. It was not running in Task Manager. This
happened many times last night, by the way.

At any rate, when I took it to work, it did not "lock up" on that machine.
I copied it and installed it on my machine at home tonight and it's working
fine now.

This is a real "head-scratcher" to me!

 

[TC]

Are you saying that when you used File : Open, and browsed to the
folder containing the database file, then clicked that file, and
clicked the Open button, that literally /nothing happened/? No message
of any description? Did Access keep responding then, or did you have
to ctrl-alt-del?

TC [MVP Access]

 

[Michael Miller]

Ok. Then, the solution is to all your development at work. )

Patient: Doctor, doctor, my arm hurts when I do this.
Doctor: Don't do that!

Old vaudville act.

 

[Dirk Goldgar]

Hi Dirk -

Thank you for responding. It was not running in Task Manager. This
happened many times last night, by the way.

At any rate, when I took it to work, it did not "lock up" on that
machine. I copied it and installed it on my machine at home tonight
and it's working fine now.

Hmm. I don't understand what could be going on. If Access wasn't still
running in Task Manager, then my original guess was wrong. So I thought
maybe you didn't have full permissions on the folder where the lock file
is being created -- you need full permissions, including delete
permission -- and maybe that was keeping you out. But if it's working
now in the same location, that can't be it, unless you are logged on as
a different user.

I'm happy that it's working now, but I'm puzzled as to why it wasn't
working before.

 

[Rob Oldfield]

It's possible that it was, in fact, opening - but just with the database
window positioned 'off screen' due to a change in screen resolution (though
there would have been scroll bars there in that situation). It usually
throws me for a second or two when I see one like that. Does it have any
kind of maximised startup form?