3197: The microsoft Jet Database Engine stopped the process because you and another user are attempt

[josiah.mcdonald]

Hello,

I have a fairly large (For Access - its slated to be transferred to
MySQL) backend that allows the user to use the database's front end
normally to store and retrieve data. However when I try to open the
database I get the Error "The microsoft Jet Database Engine stopped
the process because you and another user are attempting to change the
same data at the same time".


This isn't true because I have it on my local computer.


I've tried importing to a new DB file and I get the same error. The
original DB will not open to allow import (show table list) and show
error message in subject line of this post.


I've been reading through other forum posts and tried JetComp.exe and
that also gave me an error.


Also I've read that since the users can use the file normally its
probably an issue with one or more of the system tables. However no
one has addressed how to solve this case.


Can someone please help me as soon as possible as this DB file
contains very important information and if fails will cause the group
to be "Dead in the water"


Thanks in advance,


Josiah

 

[Steven Chicago,Illinois]

Josiah, I am not familiar with that error message. But I have noticed when I
am on my own PC using a access database, it creates a .LDB version of my
database to lock the database, sometimes I have exited and that file has not
been deleted. And until I get it to delete, it thinks someone else is on too.
As for getting the data out of the database before it goes bad, try copying
it using windows explorer to a different name. Verify that no *.ldb is also
copied to the new name. Then go into the new named database (also go in
exclusive mode) and see if it works.
You say it is getting big, to big for access. Have you done house cleaning
on it? Get rid of data fields not really needed, no calculated fields, no
redundant tables/data fields, done a compact, etc. Maybe separate the data
into databases by year or month.
There are several discussions on the .LDB 1k file that access creates. I
just noticed today that when my user was in the 2007 database running a
report that links to the 2006 database to create a current year vs prior year
comparison report, access created a DB2006.LDB 1k file while the query/report
was being run (there was also a DB2007.LDB 1k file too for the database he
was actually running the query/report in). It confused me - because I thought
someone had signed onto the DB2006.MDB and was using it. So I learned another
thing today by watching my databases (2006 and 2007) through windows
explorer, while my single user was doing the monday morning weekly reports. I
also have my user sign on to any access database in exclusive mode.

Hope some of that helps you,

 

[Jerry Whittle]

At times like this, nothing beats a good backup. In fact make a complete
backup of your database now and put it away for safe keeping.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Gina Whipp]

Aswered in Security where you posted at 7:21 AM. Try cross posting the next
time. To do this in the Newsgroups section put the different groups you
want to post to seperated by a comma.