Access Database is getting corrupt again and again

Interesting. I'll have to give this a try. I did move the .accdb to another folder on the network, which worked great for a few months. Then the Coronavirus/Work at home situation put a nix on things then the daily database corruption issues started happening again.

Really wish MS would come out with a permanent fix, instead of all these workarounds. Access is a great, inexpensive db solution and VBA isn't a major pita to learn. I really hope MS isn't giving Access a slow death like FoxPro (that was a great product too).

I incorporated the registry change into my setup program. I use the Wise Installation System, but am in the process of switching to InstallAware soon. Both have a scripting language that includes a command to update the registry. My current setup does require running the setup.exe as administrator. I don't have any VBscript code to give you to accomplish the same thing. However, you can place the commands into a .bat file and execute that. As described in other posts, you need to make the registry change on each Windows 10 client PC that uses the database in question.

Don't forget that corruption can also exist outside of the current bug and such corruption can lead to data loss.  Corruption is unpredictable.  I've seen entire databases corrupted beyond any recovery.  This is why backups are critical!

Running any Access database over VPN is asking for trouble and corruption.  Access is ONLY meant to be run over a LAN.  Everything else is a risk, VPN is one of the highest risks for encuring corruption just by its nature.

You should always make a backup prior to compacting.

My experience was as follow:

General corruption: can go both way, but usually without record loss.

"windows 10 corruption issue" discussed in this thread:

• If the database is closed and repaired right after the corruption occurs, then I usually don't loose any data.

-If users keep capturing data after the corruption has occurred (after the first error message occurs), then these records are usually lost, will look like #### in the back-end.

Via VBA, I force the application to close and put it under maintenance (keep users out) whenever the error 3343 or 3049 occur.

Hi George,

Yes, MDB back-ends and ACCDB/ACCDE front-ends will work together. The opposite (ACCDB back-end and MDB/MDE front-end) does not work.

I used to have multiple Applications, some with an MDB back-end, some with an ACCDB back-end. I had corruption issues for a whole year, after moving from W7 to W10. Then, I realised that only the ACCDB back-ends were getting corrupt.

Since I made the change to MDB back-ends, 2 months ago, I've had no corruptions at all. Working from home via VPN did not change anything to that.

Replacing DoCmd.RunSQL with DoCmd.OpenQuery did reduce the occurrence of the problem, but did not fully solve it.

It could also be that something on the server side (shared-folders containing back-ends) was changed on the IT side, without my knowledge. But I'd say that the MDB trick is worth a try.