A family of Microsoft relational database management systems designed for ease of use.
Thanks George
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Thanks George
Did you have them map to a different drive or did you stay on the original drive? If the original drive, did you create a subfolder to the original folder or a whole new folder? I may try this at one of my sites that just cannot seem to keep their DB up and running.
I created a subfolder below where my backend database used to exist then moved it there (on the same server). Once moved, I relinked the FE to the back end tables' new location and set the "Compact/Repair on Close" option. I cannot say if the folder move, relinking the back end tables and/or the Compact/Repair on Close is what fixed it, but it is fixed. Over 3 weeks later, no data corruption errors - Knock on wood. Sometimes the simpler solutions are the ones you try last.
Any ideas on what made the difference? Was the database moved to a different server or just a different share on the same server?
My prior post probably got lost or overlooked.
I moved my Access backend database to a different network folder then relinked the backend tables to the FE db. I have the Compact/Repair on Close option set. We have about 25 - 50 people accessing this database daily. Since I did this change over 3 weeks ago, there have been no more data corruption issues.
I tried to get IT Support to install the Disable Leasing fix on the Host server, but they haven't been responsive. So I came up with this above last ditch option when our database was corrupting multiple times daily, and I had to do something !
I would at least give this option a try if your IT Support group is as unresponsive as mine or the Disable Leasing fix isn't working. It was a lifesaver for me.
George
Note - Users have their own compiled FE database which is copied to their local drive (C:) when a new db version is released. I don't have users create shortcuts to the network compiled/uncompiled FE db.