Access Database is getting corrupt again and again

Why not simply implement the client fix in that case and be done with it.

Hi Jaz, I've figured out a quick process to repair my Access backend db, after having to do it so often:

* Inform users that you're repairing the backend db. Lock them out of the db if possible.

* Rename the folder which the corrupted backend db is in to "DB_DELETE_BAD_DATA" or something similar. I have only my backend .accdb file in that folder. I find that the corrupted .accdb file is locked by users and cannot be repaired.

* Create a new backend db folder with the original folder name.

* Copy the corrupted .accdb backend file to this folder.

* Repair the .accdb file and review any resulting errors.

* Do a compress on the backend db before exiting it.

* Go to the frontend .accdb.

* Highlight the linked tables and refresh.

* Compress and repair front end .accdb.

* Compile and save to .accde file if necessary.

* Test that you can access and run the database

* Let users know the database is back online.

* Delete "DB_DELETE_BAD_DATA" folder when you are able to (.accdb file may stay locked for a few minutes or several hours).

I hope this is helpful.

George

One word - Government.

Hi, George:  What I've been doing is dragging a copy of the backend to the user's desktop (I'm remoted in), repair it there and then drag it back to the server folder.  I find that sometimes if I try to repair on the server(s) folder the database goes into a non-responsive state.  Then I store that repaired copy on the desktop into a dated folder so there's always an off-server backup from the date I did the repair.  That way I don't have to refresh links.  When all goes right it's about a two minute procedure.