A family of Microsoft relational database management systems designed for ease of use.
I posted a whole bunch on my blog, see http://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
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.
I posted a whole bunch on my blog, see http://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
I posted a whole bunch on my blog, see http://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
Thanks Daniel. Much appreciated.
We've applied the Official Microsoft Workaround, made the registry changes to our 2016 Server & workstations. It's been over a week and so far
we had no problems with our data file accdb getting corrupt. We have 6 workstations running Win 10 1709 & 5 running 1803.
Finger Crossed!
Tom
We also applied the official Workaround on our Server 2016 and windows 10 stations. after te workaround the databases are working without any problem.
Thanks!
Had this problem months back, (nightmare waste of time) eventually worked out Windows so managed to roll back to 1703.
I have avoided using the workarounds and rolled back each time
However a few PC's have now updated to 1803 & even though rolled back, 2 days later it updated again so I am going to try & use the 1803 as I am going away & can't leave staff in this situation!!
I have windows Home on a few PC's so can't easily prevent this update!!
My most recent Windows 10 update still has the problem as of 13/8 so I DO NOT think any recent windows updates have helped.
Going to try the disable leasing.
My server PC does in fact run Windows 8, is is all the network PC's that run Windows 10 now,
Just tested & it seems will need (not tried yet) to use disableserver on this windows 8 PC server as was corrupting.
Whilst recommended, I was a little surprised as this server PC not being win 10, in all my testing before it was the client PC's on 1803 that caused the problems, the server always stayed the same.
Not yet tried on server PC as tied up for a while but will report back.