A family of Microsoft relational database management systems designed for ease of use.
Thanks for the tip, Daniel !
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 for the tip, Daniel !
That may be what is occurring. The problem is knowing when the data corruption occurs, so you can quickly shutout the users & start repairing. Maybe implement a text or email alert ?
Interesting. I'll have to give this a try. I did move the .accdb to another folder on the network, which worked great for a few months. Then the Coronavirus/Work at home situation put a nix on things then the daily database corruption issues started happening again.
Really wish MS would come out with a permanent fix, instead of all these workarounds. Access is a great, inexpensive db solution and VBA isn't a major pita to learn. I really hope MS isn't giving Access a slow death like FoxPro (that was a great product too).
I incorporated the registry change into my setup program. I use the Wise Installation System, but am in the process of switching to InstallAware soon. Both have a scripting language that includes a command to update the registry. My current setup does require running the setup.exe as administrator. I don't have any VBscript code to give you to accomplish the same thing. However, you can place the commands into a .bat file and execute that. As described in other posts, you need to make the registry change on each Windows 10 client PC that uses the database in question.
Don't forget that corruption can also exist outside of the current bug and such corruption can lead to data loss. Corruption is unpredictable. I've seen entire databases corrupted beyond any recovery. This is why backups are critical!
Running any Access database over VPN is asking for trouble and corruption. Access is ONLY meant to be run over a LAN. Everything else is a risk, VPN is one of the highest risks for encuring corruption just by its nature.
You should always make a backup prior to compacting.