Tracy -

The further I get into this the more it appears that I'm going to have to do something similar to what you suggest. I was looking for something simple and quick. Oh well. Thanks!

- Mike

>We handle this differently. Instead of archiving all of the tables, we archive records to archive tables. Each of our tables has a corresponding archive table in an archive directory with a prefix denoting the table is the 'archived' version. The user elects to archive records directly from the customer's record while viewing or as a batch process from a menu based on criteria (old transactions, closed or cancelled policies, etc). To view the archived records for a customer, the selects the menu option and we use a function that opens the archived tables using the same aliases as the live tables from the customer screen. The archived records can then be manipulated just like active records. There is also an option on the maintenance menu to backup the current system which is not the same as archiving records. The backup forces all users out of the system and creates a 'snapshot' of the current tables in a backup directory or to a different media. We use this frequently when we
>need a snapshot of the customer's data for troubleshooting by the helpdesk or developers.
>
>>I would like to save all my data files in an archive folder so that each backup folder has a distinct name within the archive folder. I would then like to be able to import any of the backups based on the selection made by the user.
>>
>>To backup I could copy the current data folder to the Archive folder then rename it.
>>
>>To import I could first delete the existing data folder, copy the selected backup folder to the app folder, and rename it.
>>
>>There must be a better way. Does anyone have any suggestions.