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.
You mean the file caching workaround ?
What about the client side registry fix ? Is that also a hit or miss solution ?
George
Ok, I was able to access your link today. Not sure why I couldn't see it yesterday.
Question - If my database is on a NAS, would this client registry fix still work ?
Well, I reverted the backend db from .mdb back to .accdb, moved my .accdb be database to another folder, then relinked the front end db to the new be's new folder location. Recompiled the fe to .accde and distributed to clients' desktops. This was after I reached out for IT Support and received no response.
So far, the move to another be db folder trick seemed to be working again. Four days, no database corruption. I may have to fall back on the client side registry fix or disable leasing option if the database corruptions pop up again, but after a month and a half of daily db corruptions and no help from IT, It's good to find something that finally works again.
George
I know this is an old thread, however I am hoping that you can still help with this issues. I have one doing this and it does bloat while in use, is this something that I can stop?
I have Repair and Compact option on Close checked in my backend db, which helps with the bloating. I agree with Daniel on importing your db to a new blank db from time to time, to keep the size in check.
Btw, my switching to another backend folder has been working out ok for the past couple weeks. Only one corruption incident so far.