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. 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

  2. Anonymous
    2019-11-27T14:02:05+00:00

    Is the Microsoft suggestion (applying the registry fix to the server) the better option or to the individual client's? I don't want to have to deal with lost network drives, if that is a possibility, which seemed to be the case for many of the posters above. (And I don't even know that their IT guys will allow that change on the server).

    I can only answer based on my experience.  I did the individual client's (only the systems that were having the problem).  I have not had a report of corruption in months.  Funny how 2 systems with an identical build (from an image) can produce 1 with the problem and 1 without.  If you don't have very many systems to update or if you just want to test it out, I'd do the individual clients.  You can always add it to the server later if you need to do a bunch.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-27T13:56:42+00:00

    According to Microsoft, yes, you need only apply the registry fix to the computer housing the back-end file.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-27T13:16:55+00:00

    I just started experiencing this issue with a client who recently switched from their Windows 7 computers (where all was completely stable) to Windows 10. Finding this thread was such a relief (I originally ruled it out since the first post was June 2018, so I assumed all would have been fixed by then).

    Is the Microsoft suggestion (applying the registry fix to the server) the better option or to the individual client's? I don't want to have to deal with lost network drives, if that is a possibility, which seemed to be the case for many of the posters above. (And I don't even know that their IT guys will allow that change on the server).

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-20T00:51:07+00:00

    Are you linking to the file that has the issue?  Because that won't work.

    Was this answer helpful?

    0 comments