I have a database that needs to be archived annualy. (I had been manually compacting the current file into a “2001.mdb”, “2002.mdb”, etc)
I want to automate this for the users so it needs to be idiot-proof. My system is split into a front-end/back-end setup and here’s what I really want to give them:
1) A command button that will perform the backup process, could prompt them for the filename to save as.
2) The ability to switch the data file to use as the back-end so they can use the same front-end to view the data from 2001, 2002, etc.
Is there a simple way to change the file being used for the back-end? There are a lot of tables but they all come from the same file. All of these files are the same structure, just with each year’s specific data.
Anybody know how to pull this off?