Microsoft 365 and Office | Access | For home | Windows
A family of Microsoft relational database management systems designed for ease of use.
Can you send us the name of the platform?
Access Database is getting corrupt again and again
![](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)
Anonymous
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.
604 answers
Sort by: Most helpful
-
Anonymous
2020-07-11T19:27:29+00:00 -
Anonymous
2020-07-11T19:17:17+00:00 This is some great information. Thank you for sharing.
Could i ask with which company you are dealing with as I'd like to add this information to my blog page on this bug.
-
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
-
Anonymous
2020-07-10T16:29:10+00:00 This is a REAL solution. If it doesn't work for you, try one of these other posted solutions.
-
Anonymous
2020-07-10T15:52:02+00:00 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.