A family of Microsoft relational database management systems designed for ease of use.
Thanks Graeme.
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.
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
Thanks Graeme.
I have not noticed any slow down on the client PCs (Windows 10 v1803/v1809). That was a relief for me after reading the potential speed issue. I have noticed when working on the server directly that there seems to be a slight slow down in performance, but nothing to complain about. Also, we are only ever logged on the Server occasionally for server maintenance etc. The monthly server updates seem to install quickly enough and the server restarts are no longer than would be expected... Having said that, I am usually restarting the server remotely of an evening and always wait 5 minutes after the 'ping' shows the server has successfully restarted, to allow for services to fully restart. I hope that helps.
No, I only applied the registry fix to the Server 2012 and this stopped the corruptions on the client PCs.
Thanks. So it was the server only? You didn't apply the workaround on the workstations?
Did you see any negative impact on server performance? This seems to vary according to different accounts from people who have employed the workaround. Also....how big is the organisation......number of workstations?
No, I only applied the registry fix to the Server 2012 and this stopped the corruptions on the client PCs.