This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
A family of Microsoft relational database management systems designed for ease of use.
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.
So I read your lengthy post. You opt for the Server fix at first then add several coding, registry and database object changes to improve the performance. Then you remove the Server fix, and it magically continues to work flawlessly & quickly for the past 4 weeks ? Have I summarized your fix correctly ?
Please have a look at the post above
In a nutshell, what is the fix you are suggesting, which you have had four weeks of success with ?
I am still rolling back my users to Access 2013 32-bit, and so far, it's been good. I wish the rollback was going faster than it is, but with IT, you can't have everything. At least they're responding to my requests now, so that's a plus.
George I totaly agree with you.
But there is nothing left.
We are by our own. So either we are seaching for a job or we try to gain some time with custom fixes while searching to bail out from Microsoft ...
But I suggest to give it a try. Because it is the 4th week without any db corruption and the speed is skyrocket, by far faster even before the Server Fix ...
While I appreciate all the suggestions and possible solutions, this is Microsoft's responsibility to fix this issue. Developers shouldn't have to come up with workarounds which may or may not work. If MS is viewing Access as an obsolete product which they don't want to support anymore, then be honest about it and tell the Access community.