Company has legacy MS Access databases that are being replaced by PERN (Postgres, Express, React, NodeJS) web app that is just now getting built. That is to say they still need to use the legacy databases until they can be replaced... can't exactly close shop until the web app is ready.
Anyway, company implemented DFS servers last year and server mirroring due to opening a second location; wanting to share and sync files between both locations instead of the other office having to retrieve files from the server at the other office which was time consuming and causing complaints.
A quick googling of "dfs ms access" will show that DFS and MS Access do not play nicely. Before the implementation there was the occasional DB corruption one expects from using MS Access even with best practices (like splitting the backend and frontend, regularly compressing and repairing, splitting backend if nearing 2GB limit, etc.). Once it was implemented, corruption occurred several times a day, after every other save.... it was a mess and impossible to do anything.
.laccdb files from being part of the DFS. Issues still persisted. We eventually moved the databases to a shared folder on a workstation. This has significantly reduced the corruption issues, but still it is persistent enough to be annoying... especially when you have to modify the VBA, it corrupts, it loses ALL of the VBA, have to restore a backup, and then redoing the VBA that was just modified.
It is definitely more persistent than before the DFS was done. Before that, it would corrupt maybe once every month or two. During DFS it was basically constant--couldn't touch anything without it corrupting. After DFS and moving to shared workstation, now it is a once or twice a week.
Anyway, just looking for suggestions about resolving this (aside from the obvious "don't use MS access"). Could the DFS still be affecting these databases even though it is no longer on the DFS server?
Just doesn't make sense to me they would go from rarely having issues to now consistently having issues despite "resolving" the cause of the issue. Only other thing I can think of trying is having users keep a copy of the Access frontend on their
c:\ and see if that reduces issues at expense of distributing and keeping track of these files.