Automatic backup? (1 Viewer)

I am relatively new to Access 2007. During the development, occasionally I find a backup file on my drive "Name_of_DB"_Backup.accdb.

What are the criteria for the thing making a backup by itself? I think I got one or two after crashing Access, but also without a crash. Is there some obscure setting? For I most certainly did not create those backups myself.

spikepl Eledittingent Beliped Local time Today, 10:48 Joined Nov 3, 2010 Messages 6,128 As per usual, the answers reveals itself 10 seconds after posting a question:

IIRC, you get those when Access "encounters an error and needs to close". Then by default (unless you change the option settings on the dialog), it attempts to repair the open database. That process includes making a backup copy that is named with the "_Backup" suffix.

spikepl Eledittingent Beliped Local time Today, 10:48 Joined Nov 3, 2010 Messages 6,128

But: follow up - My DB Shrank from 46 MB to 28 (and the backup version is still 46) The 46-one was made by importing everything into a virgin DB.

I do not seem to have lost anything, other than some 20 MB. I am a bit mystified.

jdraw Super Moderator Staff member Local time Today, 04:48 Joined Jan 23, 2006 Messages 15,483

Do a search on Compact and Repair with Microsoft Access.

In overview, when you test and modify your Access application, Access basically kkeps all the temp tables and deleted things and cause the database size to grow. When you do a Compact and Repair, it removes all of these "unneeded pieces" and gives you the space back. I'm running 2003, but the process is similar for the newer versions.

spikepl Eledittingent Beliped Local time Today, 10:48 Joined Nov 3, 2010 Messages 6,128

Thanks for your reply, but it does not address my main concern.

I am aware of the "unnecessary" pieces but it is a mystery to me, why a VIRGIN db - (with a few changes), with everything imported (for the very purpose of getting rid of the history and "extras") sheds some 40% of its size on a crash, when prior Compacts gave zilch (as expected on a virtually virgin db with few changes)

📎📎📎📎📎📎📎📎📎📎