how to avoid another Access 2010 disaster?

Hello,

Yesterday I was looking something up in MS Access 2010, which I use often. I don't recall even changing any records - I was only looking something up. When I closed Access, I received an error message. Unfortunately I was quite busy at the time, and neglected to actually read the error message (very unlike me - I almost always read error messages).

About five minutes later I opened Access again, and received a message that my database could not be found! So I manually searched for it, and what I found was that my database was actually gone! There was a new database named database.mdb (my original database was of course .accdb), but I couldn't open it because I got this error:

The Microsoft Access database engine stopped the process because you and another user are attempting to change the same data at the same time.

I'm the only one that ever accesses this database, and as stated I didn't even change anything. I only had one form open - no tables, no queries, no reports. I researched the error message and found that it's fairly common. (Why doesn't MS fix it?)

So my question is: how can I prevent having it happen again?

I am using Access 2013 as part of my Office 2013 Pro & I searched through the help files & there was mention of earlier versions of Access that saved the database as .mdb. This lead me to ask if you have been using Access prior to version 2007. Version 2007 was when the change was made from .mdb to .accdb. I thought that perhaps there may still be old files you may have,that have not been converted over to the new .accdb format & this is causing a relapse to an old format.
Just a thought that may help, or perhaps spark a memory.

Hello Ranger4,

I created the database over 10 years ago as an .mdb in MSO 2000. I converted it three years ago when we got new computers and upgraded to MSO 2010, and haven't had any trouble with it since that time.

Once I was able to restore my original file yesterday (I'm so glad I have redundant backups!), I ran the >Compact and repair database function because I was receiving a notice that some features had been disabled, and that resolved the message.

In researching this issue, I've seen it suggested to compact and repair on a regular basis to ensure the database stays clean. Perhaps the crash was caused by a slow buildup of small issues, and that kind of preventive maintenance might be the answer to my question of how to avoid this happening again in the future. To that end, compacting and repairing is going on my list of regular things to do, and I'll keep my fingers crossed I never have to go through losing my database again!

Hi ComicJest. Actually I Compact & Repair my database as well on a fairly regular basis. I have only recently started using Access again. My first experience with Access goes back to Version 1.0 which, I think, came out in 1992, with Windows 3.1. Then to version 7 after Windows 95 was released.
I was actually surprised how quickly I was able to adjust to the latest version, as it really is still very similar. Of course I was very rusty in remembering how to set up a table, but after a few trial & errors I was able to get it done.