Access Database is getting corrupt again and again

Anonymous
2018-06-01T17:47:41+00:00

We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted.  We ran compact and repair. But it still getting corrupted again and again.  This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.

Is there anything i have check in new windows update or any other step to prevent database corruption?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

604 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-04-02T16:14:00+00:00

    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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-02T15:54:33+00:00

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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-04-02T15:46:55+00:00

    Great post, mgnagle.  I too deal with only government and it is nigh impossible to find someone willing to make the changes.  I have written a document that outlines the problem and suggests three different possible solutions (with the Microsoft recommended work-around as #1) and send that to users to forward to their IST people.  Do they do it?  No.  Right now it's just all hands on deck for my agencies to get people up and running from home so for now I'll suck it up and repair databases.  I do think I'll add the RDP access solution to the document.  Thanks for the suggestion.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-04-02T15:43:00+00:00

    Thanks David. Good info - Keep it coming !!! Like the Coronavirus pandemic, we will also get through this Access database corruption issue, with or without MS's help.

    George

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-04-02T07:58:52+00:00

    FYI: A client who previously resolved this issue by applying the official MS registry patch has recently installed a new server, and moved the back end to this. As soon as multiple users started to use the database it crashed with this issue, error 3343. Since the official work-around worked before, it was obviously easiest to ask the IT staff to apply it to the new server. This immediately resolved the issue once again, with no performance hit and no mapped drive problems reported.

    Was this answer helpful?

    0 comments