Access Database is getting corrupt again and again

Our users have started reporting similar issues with the latest round of updates to Office 2016 / Win 10 1803.  They repair the corrupted database just to have it do it again for seemingly no reason.  We can't apply the "workaround" because that is our main file server and would impact other stuff.  I will try the client workaround but its really poor development if you have to apply workarounds and they haven't addressed the issue in an year!  Seems like every "creature" update we get, they screw us over in some fashion and break something.  Hard to support systems when they constantly give you a moving target.  Small businesses can't afford to pay the extortion fee for Enterprise.  

Can't you employ the workaround on individual workstations. That is reported to "fix" the problem.

Shane Groff......are there any updates on this issue? You indicated some time ago that a permanent fix was in the pipeline.

Our users have started reporting similar issues with the latest round of updates to Office 2016 / Win 10 1803.  They repair the corrupted database just to have it do it again for seemingly no reason.  We can't apply the "workaround" because that is our main file server and would impact other stuff.  I will try the client workaround but its really poor development if you have to apply workarounds and they haven't addressed the issue in an year!  Seems like every "creature" update we get, they screw us over in some fashion and break something.  Hard to support systems when they constantly give you a moving target.  Small businesses can't afford to pay the extortion fee for Enterprise.

Were you able to identify exactly what procedures/queries/macros, etc were initiated when the file became corrupt?

As indicated in previous response, we were able to identify back to back queries where there was a delete and then append query on the same table.  Adjusting these so they were not back to back and/or introducing a delay such as doevents, seems to have resolved the issue without having to use the workaround.  There may still be something else, but it has been 6-8 weeks now without the issue.

Nope, not really. 

They posted that they had an update in early April stating that they were testing it, and nothing since.  No clue as to what is going on, MS doesn't communicate!  Your guess is as good as mine.

This very issue was the final straw with my largest client.  After being affected by various bugs and paying me, down time, and then this issue, he finally asked me to move everything away from MS.  I just finish the final release of their new web based system (a year in the making).  MS just doesn't seem to understand the damage that this issue is having on their reputation, but truthfully i don't think they care.  Access just isn't a priority IMHO.