Access 2000: Keep Getting Locked Out during Code Testing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am an experienced Access 97 programmer. Access 2000 is annoying me

I have a form which I am writing routine VBA/DAO code in and everytime I test my code, A2k tells me I do not have exclusive access to the database so I wont be able to save any changes

If I set up with exclusive access to the database, everytime I test my code it tells me another user is using the database

It doesnt matter whether the code runs or not or what the codes does

This never happened to me in years of using Access97. My productivity is through the floor
Helppppppp......
 
-----Original Message-----
I am an experienced Access 97 programmer. Access 2000 is annoying me.

I have a form which I am writing routine VBA/DAO code in
Click to expand...
and everytime I test my code, A2k tells me I do not have
exclusive access to the database so I wont be able to save
any changes.
If I set up with exclusive access to the database,
Click to expand...
everytime I test my code it tells me another user is using
the database.
It doesnt matter whether the code runs or not or what the codes does.

This never happened to me in years of using Access97. My
Click to expand...
productivity is through the floor.
Helppppppp......
.
Click to expand...

Yes, annoys me too! Access 2000 seems to have problems
with the .ldb file when you open and close the app
repeatedly. Here are some knowledge base articles related
to the issue:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;208778
http://support.microsoft.com/default.aspx?scid=kb;en-
us;274211
The only response from MS seems to be this behavior is "by
design."
I find it best to check the status of the .ldb file when I
am unexpectedly locked out - opening it in a text file you
can see who is currently showing as logged in (maybe even
you AFTER you have logged out). Also check Task Manager
to see if there is still an Access background task running
that might be maintaining a lock on the database. Other
than that I just swear a lot and wait for that .ldb file
to go away.
 
Back
Top