Error: Jet engine stopped...another user attempting to change sam

[Guest]

Full error: The Microsoft Jet engine stopped the process because you and
another user are attempting to change the same data at the same time.
This happens when I attempt to open a database that only I deal with (it
resides on a network). I then can't open the file and the above message
appears twice in succession before aborting the open. How do I tell Access to
ignore error and allow me to open it? The error has occured for days; I'm
absolutely sure no one has the database open elsewhere. Why would it say I am
trying to change data when I can't even open the file to change anything?

 

[Guest]

It could be that someone opened it by mistake and closed the database in a
not common way. Try the following:

Go to the directory where the DB resides. Look for the .ldb-file of the mdb.
If it's there try deleting it and then try to re-open the database. Just for
the sake of it if you do get it open recompile and make a copy of the
original DB.

 

[Guest]

No ldb file. It would be a hard file to even accidentally open. Any other
suggestions?

 

[Guest]

How about creating a new MDB and try to import everything from the mdb?

 

[Guest]

Had that idea. Same error appears when I pick the locked database. Also tried
to compact and repair it from a closed state and same error again. I've never
been stopped in my tracks like this before with such a simple looking error.
I think I'm screwed. Will have to get the network guys to retrieve an older
file unless you have any ideas left.

 

[Guest]

Try copying it to a local pc. Open it from there with shift.

or

Open access
choose File - open
In the Open dialog select the file but don't open it yet
now look next to the open button. You should see a little arrow. Click on it
to see the different options to choose from. Try Exclusive.

give it a go..

 

[Guest]

Also, is it a secured database? Which workgroup file are
you using?

Also, do you have the same problem if you put a new database
in the same network location?

(david)

Had that idea. Same error appears when I pick the locked database. Also tried
to compact and repair it from a closed state and same error again. I've never
been stopped in my tracks like this before with such a simple looking error.
I think I'm screwed. Will have to get the network guys to retrieve an older
file unless you have any ideas left.

anything?

 

[Guest]

Both good suggestions that I should have thought of myself. Unfortunately,
they did not work. Copied the file to my desktop; same error. Tried to open
it Exclusive, Read-only and, of course, Read-only Exclusive to the same error
(twice as always). At this point, I'd get excited just to see a different
error.

 

[Guest]

Not a secured db. Not even password protected. Created by good-ole Admin. I
had already created another database in the same network folder (and created
a test table in it) for the purpose of importing the data to it.

 

[Guest]

Is it only the Access Project inside the database that
is corrupt, or the whole database?

If it is only the Access Project that is corrupt, you can't
open it in Access, but you can still open it in DAO or
link to the tables,.

To try the DAO methods in Access, use
Application.dbEngine.OpenDatabase( .. )

(or just OpenDatabase is the same).

If you can open the database with DAO, you can
recover all of the tables and any queries, but not any forms.

(david)

Both good suggestions that I should have thought of myself. Unfortunately,
they did not work. Copied the file to my desktop; same error. Tried to open
it Exclusive, Read-only and, of course, Read-only Exclusive to the same error
(twice as always). At this point, I'd get excited just to see a different
error.

change anything?

 

[Guest]

I'm just talking about an Access MDB file. I probably sound ignorant not
knowing the difference between a project and a database. I always called it a
database. Does this answer your first question?

I am able to create a new mdb file where I can open a module and in the
immediate window I typed
Application.DBEngine.OpenDatabase
"H:\Bob\ImpactProject\arthritisimpactproject.mdb"
and hit Enter.
I didn't get an error. Is this what you meant by opening it in DAO?
I wouldn't know what to do next if this step worked. I would almost like to
just close the database since the original error seems to think it is open
somewhere else.

 

[Guest]

Have you tried importing your data from an empty mdb? In the immediatewindow
use docmd.transfer etc... there is an import option. You can hardcode the
location as it is just for recovery.

or

If you can rename you database try that, or try changing the extension maybe
that will give you the option to copy / paste it to a different location...

just another couple of options.. I hate it when someone has troubles like
this ;-(

 

[Guest]

Same error when importing to blank database (I tried that early on) and same
error when using docmd.transferdatabase... in VB. I tried using acImport and
acExport for the first argument.

I was able to rename the database, but it didn't change anything when trying
to open or connect to it. Same error. I don't know what changing the
extension would do and I don't know what I'd change it to anyway or what I
would do with it after I changed it.

-Bob

 

[Guest]

I just had a breakthrough. I am able to see the tables and queries when I
import from Excel. I really need the reports and forms, though, too.
-Bob

 

[Guest]

Well, let's start with the great fact that you are able to retrieve your
data. That's the most important thing here. What I was referring to by
renaming it is that you might rename it to [yourdbname2].mdb because that way
if locking is in the way it will not look at the original .ldb-file but
instead will try to create a new one. Why not try importing from Excel?

 

[Chris2]

Full error: The Microsoft Jet engine stopped the process because you and
another user are attempting to change the same data at the same time.
This happens when I attempt to open a database that only I deal with (it
resides on a network). I then can't open the file and the above message
appears twice in succession before aborting the open. How do I tell Access to
ignore error and allow me to open it? The error has occured for days; I'm
absolutely sure no one has the database open elsewhere. Why would it say I am
trying to change data when I can't even open the file to change

anything?

rpurosky,

Well, one thing I have not seen suggested yet is using the JET compact
utility (on a copy of the damaged db, of course).

I see you got your data. If you absolutely must get your other MS
Access objects back, you may need to hire a recovery service. Google
"MS Access Recovery Service".


Sincerely,

Chris O.

 

[Chris2]

rpurosky,

Well, one thing I have not seen suggested yet is using the JET compact
utility (on a copy of the damaged db, of course).

I see you got your data. If you absolutely must get your other MS
Access objects back, you may need to hire a recovery service. Google
"MS Access Recovery Service".


Sincerely,

Chris O.

Oh, I'll add, you might also want to try the undocumented decompile
switch.

From a command prompt:

msaccess.exe "drive\path\file name.mdb" /decompile

This must be executed while in the directory where the msaccess.exe
file is located, and you must substitute the correct drive, path, and
file name.


Sincerely,

Chris O.

 

[Guest]

As I mentioned before, there is no LDB file, so that is why renaming had no
effect. I was able to import from Excel into a table structure that I had a
backup of, but I really did a lot of new reports that I didn't want to lose.
I put a request in to the network to get me the last usable copy of the
database, but I still wanted to know what is wrong with the current one.
Thanks for all your suggestions.
-Bob

Well, let's start with the great fact that you are able to retrieve your
data. That's the most important thing here. What I was referring to by
renaming it is that you might rename it to [yourdbname2].mdb because that way
if locking is in the way it will not look at the original .ldb-file but
instead will try to create a new one. Why not try importing from Excel?
--
Maurice Ausum

I just had a breakthrough. I am able to see the tables and queries when I
import from Excel. I really need the reports and forms, though, too.
-Bob