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-21T04:33:56+00:00

    Mark,

    I was going through all the old posts here, trying to make a case for one of the IT teams to meet with me and finally fix this issue. Then I saw something in your post: "I have incorporated this (ie. The client registry fix) into our setup program that installs our program". This may be the solution I've been searching for !

    I have a VB script which copies our Access .accde up to the user's local drive after the version of the db changes (ie. New changes to Production). How would I add this registry fix to my script, and would I need Admin rights for it to run on a user's laptop ? Also, do I need to update the registry for all client machines or still continue to have issues with data corruption ?

    Let me know - Thanks,

    George

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-09T09:51:40+00:00

    For anyone who cannot implement the workaround from Microsoft (disabling leasing), this completely solved the issue for me (with Windows 10, 1709):

    I replaced all ACCDB back-end files with MDB (older format) back-end files. I am using ACCDB/ACCDE front-end files with MDB back-end files. I have a password set on the back-end files but I do not enable file encryption. No corruption since then!

    To do this, simply create a new MDB file and transfer your back-end objects to this new file. I did not implement the Microsoft workaround (disabling leasing).

    Alternatively: replacing any DoCmd.RunSQL commands with DoCmd.OpenQuery (and a query object) reduced the occurrence of corruption by about 80%.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2020-04-02T22:17:20+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-04-02T16:14:36+00:00

    One word - Government.

    Was this answer helpful?

    0 comments