Contents of the README.1ST file
---- IF YOU HAVE EXISTING DATA READ THE FOLLOWING MESSAGE ---
An error slipped in the code when converting from Turbo Pascal
version 3.02 to Version 4.0. This caused the records to be put
into the database files but the index was not always updated. If
you have any old data to be used with the program set, delete the
index files (.idx) and start any of the programs. This will
create new index files (as described in the documentation) and
the data should all be present. The safe way to change to the
new program set if you have an old version that was downloaded
from a bulletin board (the program files will have a .COM
extension) is to follow these steps:
1. Start the HSCHUTIL.COM program and dump the databases to a
Dbase compatible file.
2. Delete the program files with the .COM extension (erase *.com)
and all the index files (erase *.idx).
3. Copy the new program files from the distribution diskettes to
the hard disk working directory (copy a:*.exe c:\church).
4. Run the DBTOCH.EXE program to reload the databases with new
data. When the other program files are run the proper index
files will be created.
--- IF YOU DO NOT HAVE EXISTING DATA, IGNORE THE ABOVE MESSAGE --
As supplied, the database files are present with one record. You
may copy them to any disk to evaluate them. You may edit the
existing entry or use the add (option 1 from HSCHURCH.EXE) until
at least one family has been entered. When you are ready to
start a new database set, if you wish to start with empty
database files, copy the distribution databases to the directory
where you wish the database files to exist. Then edit the
existing family to a valid one and you are ready to enter new
Be sure to edit the file CHIDENT.DAT to your Church data before
using the program. Information on the data in this file is
contained in the file CHIDENT.DOC. This file may be edited with
a standard ASCII text editor, the HSCHUTIL program, or the
HSCHINFO program if you have the registered version.
The following files should be on the Program disk.
HSCHURCH.EXE Manages the databases.
HSCHREP .EXE Generates reports to disk.
HSCHUTIL.EXE Some database utility functions.
CHIDENT .DAT Ident file for this database.
MAIL .TBF Mail or Family database.
MEMBERS .TBF Member (first page) database.
MEMBEXT .TBF Member (second page) database.
CHIDENT .DOC Document for CHIDENT.DAT file
HSCHOVER.DOC Overview of program set.
HSCHURCH.DOC Document for HSCHURCH.EXE program.
HSCHREP .DOC Document for HSCHREP.EXE program.
HSCHUTIL.DOC Document for HSCHUTIL.EXE program.
HSCHV20 .TYP Description of database structure.
DBTOCH .EXE Reloads database with .TXT files.
SAVEDATA.BAT Backup databases, etc. to floppy diskettes.
GETDATA .BAT Restores the database from floppy diskettes.
READ .ME This file.
The Supplemental Programs disk contains the following programs.
HSCHINFO.EXE More utility and report functions.
HSCHLOOK.EXE Programmers database utilities.
HSCHMONY.EXE The Money (contributions) manager.
HSCHNOTE.EXE The Note manager.
HSCHLIST.EXE The List (attendance) manager.
HSCHGRAP.EXE List graphs and database utilities.
DBLISTCH.EXE Reloads Money, List, and Note databases.
NOTEDATA.TBF The note database.
LISTDATA.TBF The list database.
MONYDATA.TBF The money database.
LISTDESC.DAT List code descriptions.
NOTEDESC.DAT Note code descriptions.
MONYDESC.DAT Money code descriptions.
LSTDATES.DAT List dates.
MNYDATES.DAT Money dates.
HSCHINFO.DOC Document for HSCHINFO.EXE program.
HSCHMONY.DOC Document for HSCHMONY.EXE program.
HSCHNOTE.DOC Document for HSCHNOTE.EXE program.
HSCHLIST.DOC Document for HSCHLIST.EXE program.
To print the documentation files type copy filename.doc prn where
filename is the name of the document file you wish printed. The
document files are formatted for a plain printer with no special
codes in them.
The SAVEDATA.BAT and GETDATA.BAT files are not documented. They
save the databases, and the .dat files to floppy diskette using
the backup command, and recover the databases from floppy
diskette using the restore command. Use the SAVEDATA command
often to prevent data loss. It is a good idea to keep at least
one copy of the database in another location.
Good Luck --- Gerry Rohr, Homogenized Software
- 2 -