Fix Windows 10 1803 Frontend - Backend corruption issues
We have some databases with a split front end (stored on local computer) and backend (stored on a server mapped via relative path) using Access 2016 (build 9126.2259). Since upgrading many computers to Windows 10 1803 the backend database constantly becomes corrupt. We have to disable the three caches referenced in the article linked below in order for the corruption to stop, but this makes file server operations much slower while also causing unnecessary network traffic. We never had this issue on Windows 10 1703.
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/ff686200(v=ws.10)
David
shared this idea
We are well aware of this issue and are working with the Windows team on resolving the problem.
Thanks,
Access Engineering
4 comments
-
Chris
commented
This has been affecting the organization I work for since last summer. Can we get a more recent update? https://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_winother-msoversion_other/access-database-is-getting-corrupt-again-and-again/d3fcc0a2-7d35-4a09-9269-c5d93ad0031d?messageId=c9ddd419-da56-42dd-a7ca-f93d29cf2c7f&page=14
-
Alan Cossey
commented
How are you getting on 4 months into this, please?
-
Frank Rotolo
commented
Pushing Win10 & Office updates without thouroughly testing is one more reason why my users have not upgraded past Windows 7 and Office 2010 Professional. I have a fiduciary responsibility to ensure that my users have a stable platform to conduct their business uninterrupted.
-
Peter Rühm
commented
One of my clients had the same problem. IT refused to do the registry Chargers.
Converting the .accdb backend to .mdb made it possible to work with the frontend again. Luckily, I had installed some lines of code to manage the backend connection. But this solution is not satisfying: many other files are connected to the backend and can not be changed that easy...