Unrecognized Database Format only when copied to network location?

[MJE34]

We have an access 2010 database. Occasionally we get “Unrecognized Database Format” but by copying, compacting and repairing the backend fixes it. It crashed recently and I did this on a local machine. I then moved it to the network location. When I open the local copy it’s fine. When I open the network copy it’s states it needs recovering. In the past I’ve done the exact same thing and this did not happen. Any ideas?

[JoeM]

How many people are using this database?
Have you split the database (which is recommended with multi-user databases, as it helps reduce corruption)?

See:
https://www.techrepublic.com/blog/10...cess-database/
https://support.office.com/en-us/art...3-51B1D73498CC

[isladogs]

As well as the points made by Joe, regarding split databases ; other things to try:

1. After experiencing a crash, first decompile to remove any corrupted compile code - then recompile then compact & repair
2. Check whether there are any reference issues on the network copy

[MJE34]

It's a tool someone else has created who has left the business. It's split with ACCDE front end and has been crashing but compacting and repairing back end has sorted it out in the past. I've done exactly the same this time but now it doesn't work. The main symptom is if I repair back end locally it works. If I copy it to network location it doesn't. If a try and open the dumb back end in network location it says it's corrupt after repairing locally worked.

[isladogs]

Ok. Try both of the things I suggested.
If neither of those solves your problem, copy all items to a new clean copy of the BE database

[ssanfu]

Also check the BE location for the name of the BE with an extension of ".laccdb". Most of the time when the dB crashes, the locking file is not deleted. You must manually delete the lock file before trying to open the BE.

[MJE34]

It's back to normal thankfully. Don't think compiling code and references was relevant as dumb back end was corrupt that does not have code. Just opening back end results in it becoming corrupt. I suspect locking file was most likely cause as suggested by ssanfu. Thanks for your help folks.