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.
SFBAZ,
Thank you for clarifying. Pardon me if I sounded a bit harsh. Can never get *tone* right when typing.
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
Gina Whipp: I've been advocating for individual front-ends for years and only some of my clients have the back-end set to compact on close. I was speculating whether it may have been one or the other of those issues. I need to go through my list of people who have had problems to see if there is a commonality between the ones who have not had issues and those who have and the first place I'm going to look is at the back-end. I have fifty-some different clients so it's going to take a while to spot check.
Yes, individual front-ends ensure that when one user goes down they don't all go down. Until Microsoft introduced this bug, that is.
SFBAZ,
The ONLY way when having multiple Users is for them to each have their own Frontend. A link to a single Frontend is just asking for corruption.
I would NEVER set the Backend to close whether one User or multiple. However, having it do so with multiple Users is again, just asking for corruption. That said, if your Backend grows to a point of needing compacting constantly there is most likely another issue that is causing such bloat and that is what you should be looking at.
Has anyone considered the effects of having users work from their own copies of the front-end database vs. a shortcut to a single copy of the front-end database on the server? I have always recommended that users each have their own copies of the front-end but now I'm wondering if some of the problems could be related to that and maybe I should have them go back to a shortcut.
Also, could there be an issue with having the back-end set to compact on close with multi-users? I'm grasping at straws here...