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.
JD,
Ok, I thought you had your later application working for the past two months (ie. "Since I made the change to MDB back-ends, 2 months ago, I've had no corruptions at all. Working from home via VPN did not change anything to that."). What am I missing ?
George
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
Hmmm. Now that is food for thought. Thanks, Hugo.
Thanks Hugo.
Hi Paul,
Before the COVID-9 lockout, I moved my backend db to another folder, and things were going fine for a few months with no data corruption issues. However, when we all went remote and relied on our VPN connection, the daily corruption issues came back, which is what I'm dealing with currently. It certainly is a mystery.
So it looks like my choices are client registry fix, disable leasing on the backend server, roll back to Access 2013 on all client laptops/frontend/backend db's or convert the backend db to another platform, unless I'm missing any other options ? I'm assuming MS is still AWOL on this issue, correct ?
George