Corrputed DB help

[gbanks]

I have a serious problem with a db. DB is on a multi-user environment. The db became corrupted and during the compact and repair process something went wrong and it stopped the process. Now when you try to access to the db it gives you an error stating that "The Microsoft Jet engine database stopped the process because you and another user are attempting to change the same data at the same time." When you click on help it gives you an error 3197. I tried repair with JetComp 4.0 and I tried to import into a new db but it won't work. All users are out of the db at this time. Any thoughts are greatly appreciated.. Thanks...

 

[spacepro]

The only thing I can think of (I'm a bit rusty of late) is to check to see if there is a .ldb file in the same directory has the backend db. If so delete the .ldb file and try importing into a new db.

Other than that I can't help I'm afraid. Don't you have a backup up copy that you can refer to, especially in a multi-user environment , backups are essential.

Quote from Microsoft KB

Error Number 3197:
Error message:
The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.
Cause/Problem:


This error typically occurs when a long value column (an OLE or MEMO data-type) has bad data stored in it. Long value columns are typically stored in a separate page from the page that the row is stored in. If a long value column is present in the table schema, the Jet database engine will attempt to read the long value page when reading the row of data. In order to read the long value page, there is a pointer in the row of data. This error is generated when the Jet database engine cannot properly read the long value page from the pointer present in the data row. When viewing a row that exhibits this behavior in Microsoft Access data-windows, the user will typically see the number sign (#) for the entire row.

Hope I have helped you.

Regards
Andy

 

[sonny]

I read something once about trying to link/or import a table from the db using excel. Appearently excel will know theres a issue and also try to repair the db.??

 

[WindSailor]

Ouch...

Not much luck here but reading other sites I would try to do the repair locally and not on a server or other workstation.

I think I found the article sonny was talking about using Excel:
Here

Allen Brown's recovery tips, also talks about a corrupt MEMO field:
Here

Some other sites about corruption and recovery:
Here
Here

I don't have any experience using Shareware Utilities on this, but the cheapest I could find was:
Here

Hope that helps...