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.
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
This is a REAL solution. If it doesn't work for you, try one of these other posted solutions.
Rolling back Access to 2013 is not an option when I have 40+ different clients with 40+ different IT departments in 40+ different locations. Might be OK if you only have one major client and aren't dealing with government. We need a real solution, not these stop-gaps. I've fielded three database crashes in two days.
PSS: I did the "Make a New Folder" solution & it worked for me for a few weeks. I tried the server fix & performance was awful. Client fix didn't work. Again, a solution that may work for some situations, doesn't work for all situations. Many variables could be involved.
P.S. I recently tested the "Make a New Folder" solution (create a new folder on the same drive and move the back-end database to the new folder) and this did NOT resolve the issue for this client.