Access Database is getting corrupt again and again

Thanks for the feedback and confirmation, Ron.

More details on the Lifetime Cache modification if you could.

I'm loving the community interaction on issues here. Developers find a way to make it work !

Hi RonNeer!

What is the LifetimeCache modification on all FE machines?

My apologies to all if this was already in the previous threads; just not familiar with the term.

Thanks RonNeer!!

There was another issue that came up with the 1903 update. Copying files directly to a share stopped working and the solution was to create a sub-folder and point to that location. The solution I posted there is:

"My shared before pointed directly to a share on my server, the target was "\DC\share" in the property section of the shortcut I change the target to "\DC\c$\share".

It seems as though if the share is not pointing directly to the share then all works okay.

Hope this helps"

The link for that thread is https://answers.microsoft.com/en-us/windows/forum/all/drag-and-drop-to-network-folder-icon-not-working/d6db3ede-1cea-490d-bf49-339d178174b0?auth=1&page=1

This seems like the same solution may be helpful with Access corruption after seeing what worked for George.

The solution that worked for us is the LifetimeCache modification on all FE machines. We have not had any corruption errors in several months after implementing that fix.

I created a subfolder below where my backend database used to exist then moved it there (on the same server). Once moved, I relinked the FE to the back end tables' new location and set the "Compact/Repair on Close" option. I cannot say if the folder move, relinking the back end tables and/or the Compact/Repair on Close is what fixed it, but it is fixed. Over 3 weeks later, no data corruption errors - Knock on wood. Sometimes the simpler solutions are the ones you try last. 

Hmmmm.  I have always had the FE set to compact on close but stopped having the BEs set to compact on close because THAT was causing problems with multi-users on a slow connection.  Their front ends always have to be re-linked (I've built in prompts for linking) when they get an update so the relinking itself hasn't had any effect on the corruption problem.  I guess I'll recommend moving the back ends because at this point I've tried everything else.  I have over 40 customers for one of my apps and this is eating up too much time.

I didn't map another drive. I kept to the same one I had. I created a subfolder just below the folder where the BE database used to exist.

Note that I was desperate over 3 weeks ago and had to come up with a solution. This was definitely a "Hail Mary" pass which worked. I would just try it before you reconfigure your server or convert your database to SQL Server.

FYI - I compile my front end db and don't run it uncompiled. As mentioned previously, users have their own compiled FE db's which they run locally and are updated when the database version changes. Not sure if that makes a difference.

Good luck !