CBM Funet Archive/cbm-funet-archive-2003.iso/cpm/zutils/zdb18c.lbr/ZDB18.HYP/ZDB18.HYP

Text File | 1992-04-17 | 17KB | 325 lines

;



                             ---  z  d  b  ---



       vERSION 1.8 -- a zcpr3 nAME AND aDDRESS dATABASE fILE mANAGER



                           i -->  iNSTALLATION

                           d -->  dESCRIPTION

                           u -->  uSE

                           a -->    aDD

                           c -->    cALL

                           l -->    dELETE

                           e -->    eDIT

                           f -->    fIND

                           b -->    bROWSING

                           o -->    oUTPUT

                           p -->  pATCHING

                           x -->  iNDEX

                           s -->  sORTING

                           y -->  mISCELLANY

:i



 iNSTALLATION



iF YOU'RE RUNNING zcpr3.3+, zdb NEEDS NO zcpr3 INSTALLATION, BUT IF YOU'RE

RUNNING zcpr3.0, YOU NEED TO INSTALL zdb IN YOUR USUAL WAY.



bEFORE USING zdb YOU WILL NEED TO PATCH IT WITH YOUR OWN RETURN ADDRESS.

yOU MAY ALSO NEED TO CHANGE THE STANDOUT VIDEO FLAGS OR PRINTER CODES TO

MATCH YOUR TERMINAL OR PRINTER.  sEE zdb.pat FOR MORE INFORMATION.

:d



 dESCRIPTION - 1/2



zdb IS THE z-sYSTEM dATABASE, A NAME AND ADDRESS FILE MANAGER.  wHAT SETS

zdb APART ARE ITS SIZE (UNDER 8k) AND SPEED (WRITTEN IN z80 ASSEMBLER), ITS

USE OF THE z-sYSTEM EXTENDED tcap AND vlib ROUTINES FOR SCREEN GRAPHICS AND

CURSOR MOVEMENT, ITS EASY EDITING MODE, AND ITS USE OF THE INTERNAL CLOCK

TO DATE EACH ENTRY AUTOMATICALLY.  zdb WILL ALSO SEARCH FOR ANY STRING (OR

PART THEREOF) IN ANY RECORD, ANY FIELD.  aN EXPRESS SEARCH FOR LAST NAME OR

ZIPCODE USES AN IN-ram INDEX OF POINTERS FOR BLAZING SPEED.  yOU MAY ALSO

WRITE THE RECORDS TO A NEW FILE IN THE SORTED ORDER OF THE CURRENT INDEX,

REMOVING DELETED RECORDS IN THE PROCESS.  tHE OLD FILE IS RENAMED AND

RETAINED AS A BACKUP.  tHE NEW FILE IS AUTOMATICALLY REOPENED AFTER THE

SORT IS DONE AND THE FIRST RECORD DISPLAYED JUST AS ON STARTUP.  oUTPUT

OPTIONS INCLUDE LABEL AND ENVELOPE PRINTING, AND THE WRITING OF EITHER A

COMMA-DELIMITED FORMAT ascii FILE FOR USE WITH wORDsTAR'S mERGEpRINT OR A

wORDsTAR COMPATIBLE TEXT FILE WHICH CAN THEN BE EDITED AND FORMATTED TO THE

USER'S TASTE.  lABEL PRINTING AND cdf AND wORDsTAR FILE OPTIONS ALLOW THE

SELECTION OF ANY ONE OF FOUR KEYS FOR THE OUTPUT.  aS OF RELEASE 1.6 zdb

WILL DIAL THE TELEPHONE NUMBER IN THE PHONE FIELD OF THE DISPLAYED RECORD.



 dESCRIPTION - 2/2



zdb IS FULLY z-sYSTEM DEPENDENT.  iF YOU LACK A CLOCK, zdb ALLOWS FOR

MANUAL ENTRY OF THE DATE.  zdb DOES NOT REQUIRE AN rcp OR fcp OR iop TO

WORK.  iT DOES NEED THE EXTENDED tcap WITH THE 13 GRAPHICS CHARACTERS

INTRODUCED IN vlib4d.



zdb'S DATA FILE USES A 256 BYTE RECORD SO THAT EACH ONE IS ON A PAGE

BOUNDARY.  tHERE IS NO HEADER TO THE FILE.  fILE SIZE IS LIMITED TO A MERE

64k 256 BYTE RECORDS -- DUE TO THE USE OF 16 BIT COUNTERS FOR THE NUMBER OF

RECORDS AND THE FILE POINTER.  dISK CAPACITY IS THE REAL WORLD LIMITER ON

FILE SIZE.  oN A 390k FLOPPY, zdb ITSELF WILL TAKE 8k.  dIVIDE THE

REMAINING 382k BY 2 (YOU NEED TWICE THE SPACE IN ORDER TO DO A SORT) TO GET

MAXIMUM FILE SIZE -- IN THIS CASE 764 RECORDS OF 256 BYTES.  oN A HARD

DISK, OF COURSE, YOU HARDLY NEED TO WORRY ABOUT FILE SIZE.



tHE INDEX REQUIRES 16 BYTES PER RECORD PLUS AN ORDER TABLE EQUAL TO THE

NUMBER OF RECORDS IN THE DATA FILE.  wRITING THE cdf ascii FILE OR THE

wORDsTAR FILE REQUIRES A 16k BUFFER ABOVE THE INDEX AND ORDER TABLE.  a

SYSTEM WITH 45k OR MORE OF tpa SHOULD HANDLE A zdb FILE OF 1400 RECORDS

WITHOUT OVERWRITING THE ccp.  zdb HAS A BUILT-IN MEMORY CHECK TO PREVENT

CRASHES WITH VERY LARGE FILES.

:u



 uSE



eNTERING 'zdb /<CR>' AT THE COMMAND LINE WILL PRODUCE A HELP MESSAGE.  iF

YOU ALSO ENTER A DATA FILE NAME, zdb WILL LOOK FOR IT, CREATE IT IF IT DOES

NOT EXIST, AND DISPLAY EITHER A BLANK RECORD (IF IT'S A NEW FILE) OR THE

FIRST NON-ERASED ONE IN THE FILE.  iF NO FILE NAME IS SPECIFIED, zdb WILL

USE zdb.dta AS THE DEFAULT DATA FILE NAME.



iF YOU DON'T HAVE AN INTERNAL CLOCK (OR HAVE A CLOCK MODULE LOADED), zdb

WILL ASK FOR THE CURRENT DATE.  iF YOU WISH TO QUIT AT THIS POINT, ENTER ^c

AT ANY TIME WHILE ENTERING THE DATE.



tHE zdb COMMANDS ARE DISPLAYED IN A SINGLE MAIN MENU LINE AT THE BOTTOM OF

THE SCREEN.

:a



 aDD - 1/2



'a' FOR aDD IS THE COMMAND USED TO ENTER NEW RECORDS.  tHE DISPLAY IS

CLEARED AND THE CURSOR PLACED IN THE FIRST FIELD READY FOR YOUR ENTRY.

eACH FIELD IS MARKED OFF WITH ANGLE BRACKETS -- >           < -- SO YOU

KNOW HOW MUCH SPACE YOU HAVE.  iF YOU TRY TO ENTER MORE CHARACTERS THAN

ALLOWED IN ANY FIELD, YOU WILL GET BEEPED AT, BUT YOU CAN BACK UP AND FIX

THINGS.   tHE EDITING AND CURSOR MOVEMENT KEYS ARE:



     ^x, tab, return OR DOWN ARROW MOVES TO THE NEXT FIELD.

     ^e OR UP ARROW MOVES TO THE PREVIOUS FIELD.

     ^s/^d OR LEFT ARROW/RIGHT ARROW MOVE CURSOR LEFT/RIGHT.

     ^a/^f MOVE CURSOR ONE WORD LEFT/RIGHT.

     ^g DELETES THE CHARACTER AT THE CURSOR AND MOVES THE REMAINDER OF

          THE LINE ONE CHARACTER LEFT.

     ^t DELETES THE WORD TO THE RIGHT OF THE CURSOR.

     ^y DELETES FROM CURSOR POSITION TO THE END OF LINE.

     ^v TOGGLES THE CHARACTER INSERT MODE, ALLOWING YOU TO INSERT

          CHARACTERS AT THE CURRENT CURSOR POSITION, SHIFTING THE

          REST OF THE LINE TO THE RIGHT.

     esc OR ^w AT ANY POINT TO FINISH THE ENTRY.

     ^q AT ANY POINT ABORTS THE EDITING.



 aDD - 2/2



iF YOU GO PAST THE FIRST OR LAST FIELD, YOU ARE GIVEN A CHOICE OF REDOING

THE ENTRY TO CORRECT ANY MISTAKES OR OMISSIONS OR SAVING.  pRESS esc OR ^w

AT ANY POINT TO FINISH THE ENTRY.  eNTERING ^q AT ANY POINT WILL ABORT THE

ENTRY WITHOUT SAVING THE RESULTS.  zdb INTERCEPTS u/d/r/l TERMINAL ARROW

KEYS AND INTERPRETS THEM PROPERLY.  bOXES NEAR THE BOTTOM OF THE SCREEN

DISPLAY EDITING KEYS AND GIVE PROMPTS.  oN COMPLETION OF A NEW ENTRY YOU

ARE GIVEN THE OPTION OF CONTINUING TO ADD NEW RECORDS OR QUITTING.  wHEN

YOU FINISH ENTERING NEW RECORDS, THE INDEX WILL AUTOMATICALLY BE SORTED.



iF YOU WISH TO ENSURE THAT A HEADER RECORD THAT DESCRIBES THE DATA FILE IS

ALWAYS DISPLAYED AS THE FIRST RECORD WHEN THE FILE IS SORTED ON EITHER

INDEX, ENTER SEVERAL SPACES AS THE INITIAL FIRST AND LAST NAME CHARACTERS

AND MAKE SURE THE zip cODE FIELD HAS NO ENTRY.  sEE zdb.dta.

:c



 cALL - 1/2



tHE TELEPHONE DIALER WORKS WITH ANY hAYES-COMPATIBLE MODEM.  tO MAKE A

PHONE CALL PRESS 'c' FROM THE MAIN MENU.  zdb THEN INSTRUCTS YOU TO LIFT

THE RECEIVER, TURN ON YOUR MODEM, AND PRESS return.  iF THE PHONE FIELD OF

THE zdb RECORD IS EMPTY OR THE FIRST BYTE IN THE FIELD IS A SPACE CHAR-

ACTER, NOTHING HAPPENS.  tHE MAIN MENU IS RE-DISPLAYED.  tHE CALLING

ROUTINE WILL DIAL ANY PROPER SEQUENCE AS LONG AS THE NUMBERS START WITH THE

FIRST BYTE OF THE PHONE FIELD.  pUT ANY ACCESS PREFIXES AND AREA CODES IN

THE FIELD, E.G., 1-800-555-2345.  dO NOT SEPARATE PORTIONS OF THE NUMBER

WITH SPACES (1 800 555-2345) BECAUSE zdb REGARDS EITHER A SPACE OR A NULL

AS THE TERMINATION OF THE DIALING STRING.  dO NOT USE LETTERS OF THE

ALPHABET IN THE DIALING STRING.  yOU MAY USE HYPHENS OR NOT:  5551234 AND

555-1234 WORK EQUALLY WELL.



 cALL 2/2



bECAUSE zdb'S DIALING ROUTINE HANDLES THE SPACE CHARACTER AS A TERMINATOR,

YOU MAY PUT ANOTHER NUMBER OR OTHER TEXT IN THE FIELD:

          555-2345 hOME pHONE=555-5432

zdb WILL DIAL ONLY THE FIRST NUMBER.  yOU CAN PUT IN THE hAYES DELAY

CHARACTER (A COMMA) OR SEVERAL OF THEM TO USE WITH CREDIT CARD CALLS AND

THE LIKE.  pUT THE FULL DIALING SEQUENCE IN THE zdb PHONE FIELD:

          0-999-555-1234,,,,123-456-7890-4321 -- A TYPICAL CREDIT CARD CALL

WHERE THE COMMAS DELAY SENDING THE CREDIT CARD NUMBER SEVERAL SECONDS.  yOU

MAY NEED TO EXPERIMENT WITH THE NUMBER OF COMMAS.  tHE EXAMPLE WORKS WELL

WITH AN at&t CREDIT CARD.

:l



 dELETE



pRESSING 'd' LETS YOU DELETE A RECORD FROM THE FILE.  yOU ARE GIVEN A

CHANCE TO SAY NO IF YOU MISTAKENLY PRESS THE 'd'.  tHE RECORD IS FILLED

WITH NULLS EXCEPT FOR THE FIRST BYTE WHICH IS 0ffh, MARKING IT AS A DELETED

RECORD.  dELETED RECORDS ARE DROPPED FROM THE NEW FILE WHEN A NEW SORTED

FILE IS WRITTEN.  dELETING A RECORD DOES NOT CHANGE THE RECORD COUNT IN THE

HEADER LINE OF THE SCREEN SINCE THE DELETED RECORD IS STILL IN THE FILE

UNTIL A NEW SORTED FILE IS WRITTEN.  dELETED RECORDS ARE NOT DISPLAYED OR

PRINTED.

:e



 eDIT



'e' FOR eDIT WORKS EXACTLY LIKE aDD EXCEPT THAT IT IS FOR UPDATING EXISTING

INFORMATION.  yOU CANNOT EDIT THE DATE.  iT IS CHANGED AUTOMATICALLY.  aS

IN aDD, esc OR ^w EXITS THE EDITING SESSION AND SAVES THE EDITED RECORD AND

^q ABORTS THE EDITING SESSION AND RESTORES THE UNEDITED RECORD.

:f



 fIND - 1/2



tHERE ARE TWO SEARCH ROUTINES IN zdb.  'x' (eXPRESS) fIND SEARCHES THE

INDEX IN MEMORY FOR A MATCH.  bECAUSE THE INDEX IS IN MEMORY, THE eXPRESS

SEARCH IS VERY FAST.  wHEN THE INDEX IS SORTED BY LAST AND FIRST NAMES,

EACH INDEX RECORD IS MADE UP OF THE FIRST 9 CHARACTERS OF THE LAST NAME

AND THE FIRST 5 CHARACTERS OF THE FIRST NAME.  wHEN THE INDEX IS SORTED BY

zip cODE, EACH RECORD CONTAINS 9 CHARACTERS IN THE zip cODE FIELD AND

THE FIRST 5 CHARACTERS IN THE LAST NAME.



tHE OTHER SEARCH WORKS ON ANY FIELD BUT IS SLOWER, AS IT MUST READ EACH

RECORD AND SEARCH IT FOR A MATCH.  pRESS 'f' FOR THIS ONE.



 fIND - 2/2



yOU MAY ENTER UP TO TEN CHARACTERS IN THE SEARCH STRING.  fIND IS NOT CASE

SENSITIVE AND PARTIAL STRINGS ARE FINE.  eNTERING "JO" TO SEARCH FOR

"jONES" WILL GET THE JOB DONE.  yOU CAN ENTER MORE THAN ONE WORD, E.G.,

"sT. pAUL," AS LONG AS THEY ARE IN THE SAME FIELD.  iF THE SEARCH STRING IS

FOUND IN ANY FIELD OF ANY RECORD, THAT RECORD WILL BE DISPLAYED ON THE

SCREEN.  yOU MAY THEN OPT TO END THE SEARCH OR CONTINUE IT.  iF THERE'S NO

MATCH, zdb TELLS YOU SO.  eVEN IN FAIRLY LARGE FILES, fIND WORKS QUICKLY,

BUT eXPRESS fIND IS MUCH FASTER.  eXPRESS sEARCH AND fIND ARE ALSO

AVAILABLE UNDER THE oUTPUT ROUTINE.

:b



 bROWSING



pREVIOUS AND nEXT ARE FOR BROWSING THROUGH THE FILE.  pRESSING '<', OR ','

BOTH WORK FOR pREVIOUS AND '>', OR '.' BOTH WORK FOR nEXT.  rECORDS ARE

DISPLAYED IN SORTED INDEX ORDER, SO IF THE FILE IS NOT IN SORTED ORDER, THE

RECORD NUMBERS APPEARING IN THE HEADER LINE MAY NOT BE IN SEQUENTIAL ORDER.

rECORDS ARE DISPLAYED IN A CIRCULAR WRAP-AROUND MANNER.  iF YOU ARE GOING

BACKWARDS THROUGH THE FILE AND REACH THE FIRST RECORD, ANOTHER pREVIOUS

COMMAND WILL GO TO THE END OF THE FILE.  "nEXT" ACTS IN A SIMILAR FASHION

WHEN IT REACHES THE END OF THE FILE.  tWO OTHER COMMANDS, NOT ON THE MENU,

ARE 't' (tOP) AND 'b' (bOTTOM).  tHEY QUICKLY TAKE YOU TO THE FIRST OR LAST

RECORD IN THE FILE.

:o



 oUTPUT -1/2



oUTPUT HAS SUBMENUS OFFERING A CHOICE OF PRINTING LABELS AND ENVELOPES, OR

PRODUCING EITHER A COMMA-DELIMITED FORMAT ascii DATAFILE OR A wORDsTAR

COMPATIBLE TEXT FILE.  tHE LABEL OPTION GIVES THE FURTHER CHOICE OF

PRINTING A SINGLE LABEL, THOSE WHICH MATCH A KEY, MULTIPLE COPIES, OR THE

ENTIRE FILE.  bOTH THE LABEL AND ENVELOPE OPTION ALLOW YOU TO USE fIND,

xFIND, OR nEXT BEFORE ISSUING THE PRINT COMMAND.



wHEN YOU SELECT 'kEY', YOU WILL BE ASKED TO SELECT THE CITY, STATE, ZIP

CODE OR COMMENT FIELDS FOR MATCHING THE SPECIFIED KEY.  iF YOU SELECT 'x',

THE SEARCH FOR A MATCH WILL COVER BOTH COMMENT LINES IN THEIR ENTIRETY.  iF

YOU WANT TO MAKE LABELS FOR YOUR PAST DUE SUBSCRIBERS, PUT "PAST DUE"

ANYWHERE IN EITHER COMMENT LINE.  tHERE'S ROOM FOR LOTS OF IMAGINATION IN

THE USE OF THIS FEATURE.  tHE OTHER KEYS -- CITY, STATE, OR ZIP -- ARE

TREATED A LITTLE DIFFERENTLY.  wHEN YOU ENTER A CITY, STATE, OR ZIP KEY,

zdb WILL ONLY MATCH FIELDS THAT begin WITH YOUR KEY.  tHIS AVOIDS INCORRECT

MATCHES THAT WOULD OTHERWISE OCCUR.  fOR EXAMPLE, IF YOU ENTER A SEARCH KEY

FOR CITY OF "ch," zdb WILL MATCH "chEYENNE" OR "chICAGO" BUT NOT

"mASSAchUSETTS" OR "mIchIGAN." iF YOU ENTER "48" AS A ZIP CODE KEY, zdb

WILL SELECT ONLY RECORDS WHICH HAVE ZIP CODE FIELDS WHICH START WITH 48.





 oUTPUT -2/2



tHE cdf AND wORDsTAR OPTIONS OFFER A CHOICE OF WRITING THE ENTIRE FILE

(CHOOSE 'aLL' AT THE MENU) OR SELECTED RECORDS (CHOOSE 'k' AT MENU) AND

PICK THE KEY TO USE.



pRINTING OF LABELS (AND WRITING OF THE cdf OR wORDsTAR FILES) IS DONE IN

SORTED INDEX ORDER.  fOR BULK MAILINGS, USE THE zip cODE INDEX FEATURE TO

PRINT LABELS IN SORTED zip cODE ORDER.  pRINTER ESCAPE CODES (ePSON fx-85

COMPATIBLE) ARE NEAR THE BEGINNING OF zdb AND MAY BE PATCHED AS THE USER

WISHES.  a RETURN ADDRESS FOR THE ENVELOPE IS ALSO HARD CODED IN zdb AND

SHOULD BE CHANGED FOR YOUR USE OR ELIMINATED.  sEE zdb.pat FOR MORE

PATCHING INFORMATION.



tHE cdf AND wORDsTAR FILE ROUTINES USE A LARGE OUTPUT BUFFER AND DO THE JOB

VERY QUICKLY.  tHE RESULTING FILES ARE IN THE CURRENTLY LOGGED DIRECTORY.

bOTH FILES CAN BE EDITED WITH wORDsTAR, zde, OR ANY OTHER WORD PROCESSOR.

:p



 pATCHING



zdb HAS A NUMBER OF LOCATIONS NEAR THE BEGINNING OF THE PROGRAM THAT CAN BE

PATCHED USING zp, zpatch, ddt, ETC, TO ALTER THE OPERATION OF THE PROGRAM

TO SUIT THE USER.  zdb.pat MAY ALSO BE RENAMED, ASSEMBLED TO AN OVERLAY

FILE AND OVERLAID ON zdb.com TO CREATE A CUSTOM COPY OF zdb.  zcnfg.com AND

THE CONFIGURATION FILE zdb18.cfg MAY ALSO BE USED TO CHANGE SOME OF

zdb.com'S MORE COMMON USER-CONFIGURABLE SETTINGS.

:x



 iNDEX



tHE iNDEX COMMAND ALLOWS YOU TO SPECIFY THE FIELD TO USE TO MAKE UP THE

INDEX.  tHE INDEX IS AUTOMATICALLY MAINTAINED IN SORTED ORDER AND

DETERMINES THE ORDER IN WHICH THE RECORDS ARE DISPLAYED OR PRINTED.  tHE

INDEX DISPLAY INFORMS YOU OF THE CURRENT INDEX TYPE.  tHE lAST nAME INDEX

KEY PRODUCES AN INDEX RECORD FOR EACH FILE RECORD CONSISTING OF THE FIRST

9 CHARACTERS OF THE LAST NAME AND THE FIRST 5 CHARACTERS OF THE FIRST

NAME.  tHE zip cODE INDEX KEY PRODUCES INDEX RECORDS CONSISTING OF 9 zip

cODE FIELD CHARACTERS AND THE FIRST 5 CHARACTERS OF THE LAST NAME.  sINCE

YOU ALWAYS HAVE AT LEAST THE INITIAL 5 LAST NAME CHARACTERS, eXPRESS fINDS

USING UP TO THE FIRST 5 LAST NAME CHARACTERS WILL WORK NO MATTER WHICH

INDEX IS CURRENTLY IN USE.

:s



 sORT



tHE sORT COMMAND (^s) WRITES A NEW FILE IN THE CURRENT DIRECTORY WITH THE

ORIGINAL DATA FILE NAME HAVING ITS RECORDS IN THE ORDER OF THE CURRENT

SORTED INDEX.  tHE OLD FILE IS RETAINED AS A BACKUP WITH THE NAME

backup.dta.  iF A PREVIOUS backup.dta FILE IS PRESENT, IT IS DELETED.

dELETED RECORDS ARE PURGED WHEN sORT WRITES A NEW FILE.

:y



 mISCELLANEOUS



zdb'S DATA FILE USES A 256 BYTE RECORD SO THAT EACH ONE IS ON A PAGE

BOUNDARY.  dISK CAPACITY IS ONE LIMITER ON FILE SIZE.  oN A 390k FLOPPY,

zdb ITSELF WILL TAKE 8k.  dIVIDE THE REMAINING 382k BY 2 (YOU NEED TWICE

THE SPACE IN ORDER TO DO A SORT) TO GET MAXIMUM FILE SIZE -- IN THIS CASE

764 RECORDS OF 256 BYTES.  oN A HARD DISK, OF COURSE, YOU HARDLY NEED TO

WORRY ABOUT FILE SIZE.



tHE OTHER LIMITER ON FILE SIZE IS ram.  tHE INDEX REQUIRES 16 BYTES PER

RECORD PLUS 2 BYTES PER RECORD FOR AN ORDER TABLE.  wRITING THE cdf ascii

FILE REQUIRES A 16k BUFFER ABOVE THE INDEX AND ORDER TABLE.  a SYSTEM WITH

50k OR MORE OF tpa CAN HANDLE A zdb FILE OF 1400 RECORDS WITHOUT OVER-

WRITING THE ccp.  iF YOU NEVER NEED A cdf FILE, YOU CAN HANDLE A MUCH

LARGER FILE, AS MUCH AS 2400 RECORDS, DEPENDING ON YOUR tpa.  vERY LARGE

FILES TAKE TIME FOR zdb TO READ THROUGH, INDEX, AND SORT ON STARTUP, A

MINUTE OR LONGER.  wRITING A NEW, SORTED FILE TAKES ABOUT 1 MINUTE PER 100

RECORDS ON A HARD DISK DRIVE SYSTEM, LONGER ON FLOPPIES.  iF YOU HAVE VERY

LARGE FILES, IT MAY MAKE SENSE TO BREAK THEM INTO SMALLER UNITS FOR EASIER

HANDLING BY zdb.  zdb DOES A CHECK OF AVAILABLE MEMORY BEFORE ADDING A

NEW RECORD OR WRITING A cdf FILE AND ABORTS IF THERE'S NOT ENOUGH ram.



 mISCELLANEOUS



sOMETIMES THE SCREEN DISPLAY MAY GET OUT OF WHACK.  tHE MAIN MENU HAS AN

UNDISPLAYED COMMAND -- ^r (cONTROL-r) -- WHICH REFRESHES THE SCREEN

DISPLAY.