12/18/88     
     
     
     
     FILE:  COR_READ.ME
     
     PURPOSE:  COR_LOG and its associated files make up a dBASE3+
     application which is useful for tracking incoming action and all
     correspondance.
     
     FEATURES:  The program is self-contained, menu-driven and produces 
     reports which list correspondance overdue, pending, and coming 
     due within two weeks.  The report will produce route sheets to 
     attach to the correspondance or mailing labels to do the same 
     thing.  Up to three keywords may be assigned to each incoming 
     correspondance and a menu will search the database for these 
     keywords. 
     
     INSTALLATION:  Copy all the files on the disk (COR.DBF, COR.NDX
     or COR.IDX, COR.PRG, CORDUM.DBF, COR_READ.ME, COR.BA& etc. in a
     subdirectory from the dBASE3+ directory for a harddisk system.
     
     EXAMPLE (HARDDISK):
     
     C:\                            root directory
     C:\DBASE3                      dbase subdirectory
     C:\DBASE3\COR_LOG              COR_LOG subdirectory
     
     For making subdirectories, copying files etc. refer to your
     system documentation for DOS or to the dBASE3 documentation.
     
     STARTUP (harddisk):  From the DOS prompt in drive C:
     
           C:\>PATH=C:\COMMANDS;C:\DBASE3;         [return]
     
           C:\>CD C:\DBASE3\COR_LOG                [return]
     
           C:\DBASE3\COR_LOG>DBASE COR_LOG         [return]
     
     You will be greeted with a menu which requests the current date,
     the drive containing the program and data files.  Use "C:" and
     "C:" for harddisks, and "A:" or "B:" for floppy systems.
     
     DATA STRUCTURE:
     
     Structure for database: C:\DATABASE\DBASE3\COR_LOG\COR.DBF
     
     Field  Field Name  Type       Width 	Use
     
         1  CONTROL_NO  Character      7	Control no. YY-nnnn

         2  SERIAL_NO   Numeric        4	nnnn - last 4 digits of 
     						the CONTROL_NO
     
         3  TYPE_COR    Character      1	Type of correspondance,
     						i.e. M-message, L-letter
     						etc.
     
         4  CLASSIF     Character      1	Classification, i.e.
     						S-secret, U-unclassified
     						etc.
     
         5  COR_FROM    Character     30	Correspondance is from:
     
         6  COR_TO      Character     30	Correspondance is to:
     
         7  COR_SUBJ    Character     50	Subject line
     
         8  COR_REF_NO  Character     14	Originators code on 
     						incoming correspondance
     
         9  COR_SER_NO  Character      5	Serial of letter
     
        10  COR_FILE    Character      5	Standard five digit file
     						code or SSIC if used
     
        11  COR_DATE    Date           8	Date of correspondance
     
        12  ROUTE_1     Character      4	First code to be routed
     						to or originator on outgoing
     
        13  ROUTE_2     Character      4	Second code .....
     
        14  ROUTE_3     Character      4	And so on .....
        15  ROUTE_4     Character      4
        16  ROUTE_5     Character      4
        17  ROUTE_6     Character      4
        18  ROUTE_7     Character      4
        19  ROUTE_8     Character      4
        20  ROUTE_9     Character      4
        21  ACT_INFO_1  Character      1	Action key; A-action,
 						I-information for ROUTE_1
     
        22  ACT_INFO_2  Character      1	Key for ROUTE_2 ....
     
        23  ACT_INFO_3  Character      1	And so on ....
        24  ACT_INFO_4  Character      1
        25  ACT_INFO_5  Character      1
        26  ACT_INFO_6  Character      1
        27  ACT_INFO_7  Character      1
        28  ACT_INFO_8  Character      1
        29  ACT_INFO_9  Character      1
        30  KEYWORD_1   Character     10	Keyword classifying
     						correspondance.  Be
     						creative.  Try contract
     						number, HOT JOB, or any
     						device which may useful
     						for quick record
     						retrieval
     
        31  KEYWORD_2   Character     10	Second keyword ....
        32  KEYWORD_3   Character     10
     
        33  PRNFLG      Logical        1	Print flag - "TRUE" if
     						this record has had a
     						route sheet printed
     						already
     
        34  DUE_DATE    Date           8	Date the correspondance
     						is due
     
        35  RESP_CODE   Character      1	Response code - "C" for
     						complete, "O"-open,
						"X"-outgoing, "D"-dummy record
     ** Total **                     226
     
     
     USING COR_LOG:  You will find all the menu items self
     explanatory.  Lessor used items such as "DELETE Records" are
     found on the Utility submenu.  The KEYWORD search feature is
     found on the Report submenu.
     
     Depending on the volume of your incoming correspondance, you will
     want to file away or archive your completed action correspondance
     perodically.  A single data floppy should hold about one thousand
     records, a harddisk much more.  I suggest archiving the completed
     work once per year for average sized mailrooms, once per quarter
     for large operations.  The archive feature is found on the
     Utility submenu.
     
     FOXBASE vs. DBASE:  I wrote this program using FOXBASE+ v2.00
     which uses the same syntax as dBASE but is much faster.  The program
     will run either way, since the logic will sense if you are using
     dBASE or FOXBASE.
     
     SETUP and defaults:  You can change the colors on the screen, the
     auto-fill on the "correspondance to:" line and a few other values
     simply by deleting the CORMEM.MEM file.  The program will make a new
     one by guiding you through a menu.
     
     PRINTERS:  The feature which prints mailing labels sends EPSON
     control codes to an 80 character printer.  This feature may not
     work with other printers.

     AUTHOR:  M.W. Praskievicz, OICC Southwest Pacific, APO San
     Francisco, CA 96528.