We’ve been having issues with corruption on our MS Access Database lately. It started in early November with the new version of Office out into the wild as you stated. I’ve been getting people back on Version 1902 of Click to Run to keep it consistent. Last week we had a new corruption we haven’t seen before come up. It’s happened twice now –last Friday 1/3 and yesterday 1/9. I know enough about MS Access to be dangerous – so bear with me here on lingo.
Patterns I could find lately:
- MS Access will allow people to make changes but it gave two end users the lock out pop up at different times and both were not in the same area updating. Two end users have communicated with me that they get the error and they sit right next to each other. There could be potentially more than just these two users.
- Within at least 2 hours of those errors, the database will try to do a backup on it’s own and corrupt itself. VBA run time error crops up.
- I’d say if I had to pin point an exact timeframe the error started around 10:59 AM 1/09/2020 since that's when the backup was created by MS Access.
- I pulled our Acronis backups from noon and midnight. I was able to get us back on track with a database that updated at 11:30 AM. We lost data from 11:30 til I was notified later at 12:30. There was still people in the database at this current time who didn't get any errors. Others who want to open the database get "Unrecognized database format .... Database.accdb"
- From what I can find these are the errors that show up below when I try to open the database before I will attempt to Compact & Repair which fails to fix the issue and erases all of the VBA.
- note the way I’m doing this is changing the current database extension over from .accdc to .accdb in order to get into the database for the repair and then changing it back once completed.
- I have to go and find a backup suitable to replace the current database corruption.