DAMAGED DATABASE - PLEASE HELP!!

  • Thread starter Thread starter Jon Wells
  • Start date Start date
J

Jon Wells

I am getting the error message: "The MIcrosoft Jet
database engine stopped the process because you and
another user are attemtping to change the same data at the
same time." No one else is connected to the database. I am
using Access 2000. I cannot repair or compact the database
without receiving the same error message. I am on a LAN
with other users and we all receive the same message. Is
there any way to recover the database or open it some
other way?? Please respond if you can help. Thankyou.
 
Jon Wells said:
I am getting the error message: "The MIcrosoft Jet
database engine stopped the process because you and
another user are attemtping to change the same data at the
same time." No one else is connected to the database. I am
using Access 2000. I cannot repair or compact the database
without receiving the same error message. I am on a LAN
with other users and we all receive the same message. Is
there any way to recover the database or open it some
other way?? Please respond if you can help. Thankyou.
Click to expand...

First thing to do: get everybody out of the database, then make several
backup copies of it.

Second thing: verify that you aren't getting this message because of
some code that is running. Sometimes a message like this arises because
you are modifying the same record both in code and via the user
interface. When do you get the message? If you have no forms open and
work directly in tables, does the message come up?

Third thing: with everybody out of the database, see if the .ldb file
that corresponds to the .mdb is still present. If it is, try to delete
it, then go in again and see if the problem has gone away. If so, you
may be all right now.

Fourth: try importing all objects from the old database into a new blank
database. This often gets rid of corruption. Any object that won't
import will probably have to be recreated from scratch.

Fifth: try decompiling the database, using the /decompile command-line
switch. It may help, if the corruption is in the VB project.

For more about database corruption, see Tony Toews's FAQ page on the
subject:

http://www.granite.ab.ca/access/corruptmdbs.htm
 
This has happened to me some times.
I don't know how technical this solution is, but it has
worked for me.

With everybody out of the database, make a copy to
another folder.

Then open this 'new' database and compact/repair it.
Then put it back on its original location!

As I told you, I don't know how technical it is, but it
has worked to me!
 
Back
Top