Which files to backup

In addition to describing the function of each file used by the program, this chapter contains a 'backup code' which indicates what files should be backed up on a regular basis.  The following backup codes exist:

Code                 Description        

D                 This is a database file.  Its contents can not be replaced with other data.  If this file is lost or corrupted, there is no way to replace it.  Back this file up.        

C                 This is a configuration file.  This file was created specifically for your installation.  When you make changes to 'customize' your system, you will likely modify this file.  While Pd' Programming may have a copy of this file, we don't always keep up to date with all of your changes.  If we don't have it, it probably can not be easily replaced.  Back this file up.        

R                 This is a report or query-related file.  This file was created by you, and may have involved some effort that would be inconvenient to recreate.  It is a good idea to back this file up, but it can be replaced with effort.        

O                 This file was not created by Intersection Magic.  Backup schedules are at your own discretion.        

N                 This file can be replaced with a little assistance from Pd' Programming.  It need not be backed up if resources are not available.        

In addition to the files listed in the following sections with backup codes, your charts directory; ara directory; assist directory; and winpds directory may be modified by the program at your request during the running of the program.  As a result, it is probably a good idea to backup those directories.

Obviously, the intent of this section is to assist those people who have limited backup resources and can not back up their entire directory structure.  The best possible backup is to save copies of all files in the magic directory and all of its sub-directories.