Category : Databases and related files
Archive   : TX69.ZIP
Filename : MESSAGES.TXT

 
Output of file : MESSAGES.TXT contained in archive : TX69.ZIP
---LINES 2 to 6 is an EXIT MESSAGE
Do you agree to 's license, disclaimer, & agreement
and
Do you wish to exit  now?

Yes No
---LINES 8 to 23 is another EXIT MESSAGE
REDUNDANCY IS ESSENTIAL IN SCHEDULING IMPORTANT EVENTS

You should never rely solely upon a computer system to maintain data that
is critical. Loss of important information may result from hardware malfunc-
tions, programming flaws in the software, or Acts of God. If, during this
session with the program you have entered events of which your failure to be
notified could result in embarrassment or liability, you should also enter
those same events into a manual calendar or tickler file. And you should
refer to your manual system on a daily basis to ensure that you miss nothing.
Also, don't forget to back up your program data on a regular basis. On
odd days, you should use a backup disk labled "ScheduleODD", and on even days
you should use a "ScheduleEVEN" backup disk. Every Friday, you should backup
to a "ScheduleWEEKLY" disk, and at the end of every month, you should use one
labled "ScheduleMONTHLY". The WEEKLY and MONTHLY backups help protect you in
the event that you unknowingly back up bad data to the ODD and EVEN disks.

--- Lines 25 to 33 discuss setting up for printing a monthly calendar
The number of columns determines how wide each day's block will be (eg: 15
columns equals a width sufficient to print 15 characters). The number of
lines determines how long each day's block will be.
If you request too large a number of columns below, your printer may over-
print some lines. If you request too many lines, the calendar may not fit
onto one sheet of paper. It's probably wise to use the default number of
columns suggested by the program. The default number of lines should also be
used, unless you're doing only a one- or two-week calendar, in which case you
might want to double or triple the suggested value.
--- Lines 35 to 41 contain the heading for the OMISSION of LOG items
Now, the program will look through its LOG of disbursements, receipts and
services performed and eliminate the items already tagged for omission. Also
eliminated will be ALL items (whether tagged for omission or not) falling
BEFORE the cut-off date set below.
Note that the suggested cut-off date is about one YEAR back.


--- Lines 43 to 49 contain the heading for the OMISSION of SCHEDULE items
You are about to go through an omission process, during which items already
tagged for omission will be eliminated from the SCHEDULE. Also eliminated
will be ALL items (whether tagged for omission or not) falling BEFORE the
cut-off date set below. After this omission process for the SCHEDULE,
the program will do the same for the LOG of disbursements, receipts, etc.
Note that the suggested cut-off date is about one YEAR back.

---LINES 51 to 55 is another EXIT MESSAGE
Would you like to use DOS's backup program to make

an archive copy of your data

No Yes

---Lines 58 to 69 are for the re-indexing routine
Indexing the Schedule and Log databases is a DRASTIC measure. The ONLY time
you should even consider it is when your databases are corrupted and you have
no reliable backup disks from which you can restore them. The routine you're
about to go through will read each Schedule & Log entry in your current files
and attempt to index it. If the routine finds any faulty links to other re-
cords, it will simply erase them, possibly leaving reminders that no longer
link to primary events. This routine will take a LONG time if you have set up
many plans.

Do you wish to proceed with this drastic measure?

No Yes

---Lines 72 to 77 are for JULIAN DATE info
This function displays (at top-right of screen) the Julian date/week or the
number of days/weeks from a reference date to the calendar's highlighted date

If you want simple julian dates to be displayed, DO NOT fill in a date
below. Fill in the date below only if you wish to show the number of
days from a specific reference date to the calendar's highlighted date.

---Lines 80 to 84 are for JULIAN TITLE info
For the title, enter whatever you'd like to call this date calculation.
If you do not enter a title, date calculation will not appear on screen.

If you're doing week counting, instead of
day counting, begin your entry with a #.

---Lines 87 and 88 are for PLAN/TEMPLATE selection
You have named a plan which does not exist. Therefore, it is assumed that
you wish to create a new plan with that name and patterned upon a template.

-- Lines 91 to 97 are for field erasure in CLIENT MODULE
At least one customizable field has been erased (that is, its heading is
blank). If a field that was being used previously has just been erased,
you might wish to erase each  record's data for that field.

Do you wish to eliminate each record's data for all erased fields?

No Yes

-- Lines 100 to 104 are for record setup in CLIENT MODULE
Each  record has nine optional fields (3 short and 6 long) whose head
ings you may specify. Just type in the new heading for the field indicated
by the flashing arrow. To eliminate a field, simply erase its name. If you
ever need to change the headings you enter below, you may do so by pressing
the Ctrl-U key combination at the  Menu.

-- Lines 107 to 111 are for setting Plan dates
 will now set dates for related events in the plan. Do you
want to PAUSE at each such event so that you may enter its  and
time, or do you want the program to AUTOMATICALLY set s and times?

Automate-DoNotPause PauseForInput


-- Lines 115 to 122 are for Reminders within the Plan routine
One (or more) of this Plan's events may have "RMN" in its notes, indicating
that you might like the program to set a reminder for it at a prior date.
Even though you elected above to automatically fill in dates & times, would
you nonetheless like the program to pause to ask for reminders?

PauseForReminders DoNotPause



-- Lines 125 to 129 are for Plan edit routine in editor
This plan already has already had dates assigned to its events, so it can-
not be edited. It may be altered only through the normal routine by which
dates are placed into plans (pressing "P" at the Schedule menu).

Esc




-- lines 135 to 137 are for report preparation
To use standard paper for a STANDARD-size (8-1/2" X 11") report, pick `11'
To cut standard paper into DAY-PLANNER-size (8-1/2" X 5") reports, pick `5'

11 5





-- Lines 145 to 151 are for the Manual Printing Message
The manual may be printed any time from within the program by pressing "U,M"
at the main calendar screen. "U" takes you to the Utilities module, while
"M" selects ManualPrinting within that module.

Would you like to print the manual NOW?

Yes No


-- Lines 155 to 160 are for Printdrive routine
It's possible that your printer will not accept a software command which in-
structs it to switch to the IBM graphics character set. Just in case this
is true, you should ensure that your printer's dip switches are set so that
your printer will automatically default to the IBM graphics character set
whenever it's turned on. You'll need to handle this chore only once, unless
your other programs happen to require different character sets (not likely).



-- Lines 165 to 172 are for WINDOWS installation routine
An effort has been made to install this program for use with Microsoft Win-
dows, following the guidelines you have provided. Make a note that, to use
the program within Windows, all you need to do is to press

ALT-T

Also, please read the section of the manual that discusses Windows.







-- Lines 180 to 183 are for DOS 6 users who try Backup/Restore
The backup and restore utilities supplied with this version of DOS do
not support the command line parameters that this program supplies.
You must perform backup and restore operations manually. The files
to be backed up are all those whose names end with ".LBF" or ".LBI".




  3 Responses to “Category : Databases and related files
Archive   : TX69.ZIP
Filename : MESSAGES.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/