Access Database is getting corrupt again and again

You mentioned building in a delay; what method did you use to delay the processes?  I can think of a couple of ways to do it but if you've got one that seems to work that would save me having to guess what's going to help.  I do have a back-to-back series of delete/appends going on with tables via VBA.

I just had a user's database go down and I confirmed with them that they were indeed working on the procedures that trigger the delete/appends so your pinpointing of this possibility is the clue I've been waiting for.  Thank you for sharing.

We have several locations with their own MSAccess database on a server and 15-30+ simultaneous users connecting via a frontend MSAccess database.  It had been years without any such corruption until the end of 2018, when the corporation's IT began updating the window 10 computers with the 1803 version(s).  Dealt with the issue intermittently over a couple of months.  Was likewise hesitant to use the work around either on the server or the clients.

We were able to identify a combination of delete and append queries to the same table, back-to-back that would cause this issue.  After we rearranged the queries and/or entered some delay between such, we have not had the issue re-surface for weeks. 

Not sure if we are out of the woods yet, and still look forward to the "fix".  But for now, addressing this by adjusting such back to back delete/append queries, seems to be working.

SO, just another piece of the puzzle that might provide some insight.

Thanks for the insight, TQuasar! In your experience, does the corruption occur with consecutive appends as well, or only when there are consecutive appends and deletes? I imagine it would be difficult to reduce consecutive appends in a multi-user environment. 

Thanks, TQuasar! I'm going to try modifying our database application to reduce the number of consecutive delete/append queries and see if that helps to mitigate our issues.

Consecutive appends to different tables does not seem to be an issue.

We did not look for consecutive appends to the same table. (Though there are several such scenarios in the database)  But, likely it is not a problem or we would have seen it create the corruption issue by now.

Wow!  That's interesting.  Thank you for sharing this. I will go back and check the application's queries to see if any of them fit this description.  Any clues are helpful.

We have several locations with their own MSAccess database on a server and 15-30+ simultaneous users connecting via a frontend MSAccess database.  It had been years without any such corruption until the end of 2018, when the corporation's IT began updating the window 10 computers with the 1803 version(s).  Dealt with the issue intermittently over a couple of months.  Was likewise hesitant to use the work around either on the server or the clients.

We were able to identify a combination of delete and append queries to the same table, back-to-back that would cause this issue.  After we rearranged the queries and/or entered some delay between such, we have not had the issue re-surface for weeks. 

Not sure if we are out of the woods yet, and still look forward to the "fix".  But for now, addressing this by adjusting such back to back delete/append queries, seems to be working.

SO, just another piece of the puzzle that might provide some insight.

Thanks for the insight, TQuasar! In your experience, does the corruption occur with consecutive appends as well, or only when there are consecutive appends and deletes? I imagine it would be difficult to reduce consecutive appends in a multi-user environment.