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
jondenny1,
Hmm, interesting. In the case where only machine was crashing I applied the workaround directly to that machine and that solved the problem for the one. (The many were solved when applied to the Server). Have you tried that?
The only thing that needs to be done is the Disable Leasing registry hack on the server hosting the back-end file. (Implementing multiple fixes may cause other issues, who knows what exactly)
If after that you are still experiencing corruption, than this, IMHO, will be genuine corruption, not related to the bug.
I'd start by importing everything into fresh database containers and see if that helps any. Ensure that the VBA is using Option Explicit everywhere and compiles without errors. Ensure everyone is on a common wired LAN (no wireless!, no Dropbox, OneDrive or GoogleDrive ..., ect.). Ensure a persistent connection is establish at the very startup of the front-end. And so on ...
Daniel, thanks for reminding me to create a persistent connection. I'll include that in my next update. That said, I did have one application with a persistent connection crash the back-end data file. The front-ends never crash, only the back-ends.
The only thing that needs to be done is the Disable Leasing registry hack on the server hosting the back-end file. (Implementing multiple fixes may cause other issues, who knows what exactly)
If after that you are still experiencing corruption, than this, IMHO, will be genuine corruption, not related to the bug.
I'd start by importing everything into fresh database containers and see if that helps any. Ensure that the VBA is using Option Explicit everywhere and compiles without errors. Ensure everyone is on a common wired LAN (no wireless!, no Dropbox, OneDrive or GoogleDrive ..., ect.). Ensure a persistent connection is establish at the very startup of the front-end. And so on ...
SFBAZ,
Thank you for clarifying. Pardon me if I sounded a bit harsh. Can never get *tone* right when typing.
Gina, dat's OK. :)