Backup

PRIMARY DATABASE: DB2000 has two database files. DBxxx.mdb and DBxxx.bak where xxx is the squadron or district code of the database content. Dbxxx.mdb is a Primary Database and DB2000 can support any number of different squadrons or districts. After an editing session, when DB2000 is closed, a dialog appears asking if the session changes are to be saved.

A Yes response copies DBxxx.mdb to DBxxx.bak.

A No response copies DBxxx.bak to DBxxx.mdb, returning the primary database to it's state prior to the session.

In either case, after closing, both data files are identical. A Cancel response aborts closing the session.

The File menu option "Save Current Changes", copies DBxxx.mdb to DBxxx.bak. "Discard Current Changes" copies DBxxx.bak to DBxxx.mdb. There is no "Undo", these decisions are irreversible. Note that once changes have been saved in this way, only changes from this point on can be discarded when closing.

The File menu contains several other database options which require an understanding of the underlying scheme for preserving data.

Each time the database is updated from HQ. (Email or MQ server) a dated backup is made before the changes are applied. These files are named Ammddyyxxx.mdb where A is an alpha character A-Z, depending on the number of backups made that day, mmddyy is the date and xxx is the squadron or district code for the database content.

	If DB2000 is being used to support more than one primary database, then they can be selected from the File menu option "Select Primary Database" Only primary database files will be listed.
	A dated backup file can be opened by using the File menu option "Open Backup Database". This option is useful for copying records from an older version to the primary if a record needs to be restored. (See "Copy Tagged Records" below) The primary database is normally restored after backup tasks are complete using the File menu Restore Primary" option. While this file can be edited or used for any other purposes, DB2000 does not treat it as a primary database and it will want to exchange it with the primary prior to closing.
	The File menu option "Replace Primary with Backup Database" does just that. This is different from just viewing the backup. In this case, the old primary is backed up prior to the exchange so that it can be retrieved if necessary at a later time using this same option if desired. The primary database backup, DBxxx.bak is also replaced on exchange with a copy of the exchange file. In other words: DBxxx.mdb is backed up as Ammddyyxxx.mdb. The replacement file is named DBxxx.mdb. DBxxx.mdb is copied to DBxxx.bak
	The File menu "Save As" option provides a flexible way of making customized or special versions of the primary database. The file can be in the dated backup format or can be named by the user. However, the file must begin DBxxx so that DB2000 can recognize it as belonging to a squadron or district. When saved as a dated backup, it will appear in the "Open Backup Database", "Replace Primary with Backup Database" and "Delete Unwanted Database" listings. When saved as a user named file, it will appear in the "Select Primary Database" and "Delete Unwanted Database" listings. Some uses are: Distribute a special database to other members. See Q2 on FAQ page. Make a primary DB copy as a primary. Make named copies of database before and after dues season to keep historical record.

	After some period a large number of backup files will have accumulated. These may be deleted using the File menu option "Delete Unwanted Database Files".
	"Copy Tagged Records to Another Database". This option can be used to copy any records from one database to another. The records to be copied are selected by tagging them. Select the target database from the file list. Select the copy option required. If copy selection is "affiliates", select or type-in an affiliation for them. Copy Options: As affiliates only. Copied as affiliates with affiliation entered in the database. New Records Only: Copied as ordinary members but only if not already existing in target database. Overwrite Existing: Copied as ordinary members overwriting any existing data. This is explained in more detail in message at top of dialog.