I think it's corrupt :(

[DBL]

I've been approached by someone who has a backend datafile that appears to be corrupt. They tried to company and repair it and when you try and open it it's giving you the 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".

There is no one else accessing the data - there's no lock file either - and I've tried importing the data into a new database but get the same message.

The file is sitting at 119MB (don't get me started on that one) but can't get to it at all.

Anyone have any suggestions or can recommend software/company who might be able to recover it.

Needless to say they don't backup their files.

Thanks

 

[boblarson]

Well, Access World (Jon's company does this I believe). See here.

 

[Simon_MT]

Drastic as this may sound, put down the server. Get all the users to stay out, I'm going on memory as this happened sometime ago:

1) See if you can get into the database
2) See if you can create a new database and import the tables

I can't remember if I removed the ldb file. My incident happened on a Friday night, a user was editing a record on a Terminal Server Session and left the record overnight without the edit being complete. I got a ring, sailing on the Saturday and I couldn't leave as I was doing Rescue duty. There were plenty of backups so I may have been a little chavelier but the BE was sorted quite quickly.

Simon

 

[annieee]

Try to open the same database on another computer. This might help.

 

[gemma-the-husky]

in addition to the above points - the problem might be in a single record of a single table

its a bit of work, but import a few tables at a time, and see which one gives you the problem.

then if you pin it down to a single table, try linking to the table, and try a variety of things, like a maketable query, or an append query - and see if you can get it all in except for the corrupt row.

take a windows copy of the file before trying any of this - as you may cause more corruptions.

119Mb is not so big, and not unmanageable

Even copy the corrupt dbs to a separate desktop, and work with it there - you are maybe more likely to get into it on a single m/c than over a network.

and make sure they do backups in future!