Microsoft Jet database engine stopped the process... forever???

[woodrg]

i have a database with several linked oracle tables from our prod db that i only have select permission to. there is also code in the background connecting (ADODB) to tables in our test environment (tables not linked in .mdb, oracle as well), and for now, i am the only one with update or insert ability to these new tables. After testing with my inserts and updates via ADODB recordsets sucuessfully for quite sometime, I now receive the following message upon attempting to open the .mdb file itself:

The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. (Error 3197)


If you've seen this before, you know i only have OK and HELP to choose from and neither actually open my database: therefore i cannot get to any portion of the forms or code that i've been working on.

I understand what the error is indicating and that it is referring to optimistic locking of the recordset. Admittedly, its possible that during debugging i didn't get all the way out of my recordset or connection properly, but my dba has restarted our test db to clean it up, and verified that i have no other sessions running and nothing is locked on the production side. So it seems i shouldn't still be getting this error based on it's definition.

Starting over is not an option at this point. So...

How could i have triggered this error to occur and how do i get around it so i can fix it or at the very least copy that code out into a new .mdb (ready to make corrections of course!)

Any help with this would be greatly appreciated, i've got to get this project tied up and i've exhausted all my local resources.

Becky,
Ft. Rucker

 

[VBslammer]

Try starting it by holding down the shift key to disable startup code.

Try /decompile switch in command line

Try compact and repair

(make a backup copy first...)

VBSlammer

"You just have to know which screws to turn." - Professor Bob

 

[woodrg]

Thanks VBSlammer for checking out my post.

i just tried what you suggested and i get the same error.

I think the first thing it does is authenticate me to Oracle for the tables i have linked as i always have to log in before my form comes up. But this error comes up before it even gets to that point. Access opens, but that's it. btw, i can open any other access db with no problem

Becky,
Ft. Rucker

 

[VBslammer]

Have you looked for a lock file that should not be there? When Access starts up it creates a lock file called "yourDBname.ldb" in the same directory as your database, which is used to track conflicts and such. When Access shuts down, it deletes this file. If your app crashes, the .ldb file will not get deleted and generally causes problems thereafter because it is out of synch.

Look for the file in Explorer (without trying to open Access) and delete it if it's there. Then try to open the app again.

Microsoft has an outdated article about corruption and error 3197 here (for what it's worth):

Jet Database Engine Error Messages Due to Corruption

VBSlammer

"You just have to know which screws to turn." - Professor Bob

 

[woodrg]

Yes, i've looked for the ".ldb"'s, none there.

I've checked out the article you mentioned, and though the repair doesn't apply because i'm using 2003, does the "cause" still apply? i'm thinking no since there are no long values in any of my table, but i'll take any insight you may have.

I've also checked into repairing it and all i can find indicates that if it was corrupted that Access should attempt to repair it upon reopening it. But that hasn't occured.

So i'm thinking i'm back to the starting over thing, but now my concern is making sure this doesn't happen again. You can bet i'll be saving to a back up daily, but do you have any clue as to what caused this in the first place so that i don't set myself up for this to happen again? I'm certain that my LockTypes were adLockOptimistic, is there something else i should be using




Becky,
Ft. Rucker