


                           AHNDES.EXE
                       Ver 3.3  23 Feb 1996
             Copyright (c) 1991-1996 by Jack Chandler

Version 3.3

Corrects a problem which reported the date and place of the first
marriage of the spouse in the descent line in families which had
multiple marriages regardless of which marriage was the true descent
marriage.  The marriage  data of the parents is now determined by
the parents MRIN found in the next descendants individual record and
now displays the proper data.

Version 3.2

Additions:  Will now locate and print out ALL lines of descent.
Increased speed in intial record gathering and inspecting.  A few
minor modifications to correct small insignificant problems with
version 3.0.

Version 3.0

Additions:  Options for saving list of RINS in either an ASCII
text file or PAF FOCUS file.  Abbreviated index for the Descent
Chart.  Change in naming file for charts saved to disk.  Addition
of printer codes for HP Laser printers.

AHNDES.EXE is a MS-DOS PAF utility for the creation charts of both
the Ahnentafel and Descent types.  AHNDES.EXE will handle PAF data
base sizes up to 52 generations.

Although AHNDES.EXE can be run from any drive/directory, it is
recommended that it be run from the drive/directory that does
contains your PAF data.

The ahnentafel numbers are generated based upon your entry of a
base RIN.  Since most often you will want to compute/print
charts based upon yourself, it is recommended that you enter
your RIN in this position.

DESCENDANT:

The descent chart is computed and printed for a direct line from
the selected ancestor to the selected descdendant with no siblings
or other marriages considered.  This will make the appropriate jump
to the new surname when a female descendant is married.

The ancestor is selected by either entry of RIN or by search by
surname and first given name.  When search is used, the
individual found is displayed with name and birth date.  If this
is the wrong individual then the search can be continued.  No
provisions for more detailed identification is provided.
The descendant is selected in the same manner as the ancestor.

If the descendant selected is not in the direct descent line of
the ancestor it will be reported "Rin# (descendant) is not a
descendant of Rin# (ancestor)".  If ancestor is not known then
it is best to print an Ahnentafel chart prior to printing a
descent chart.  All individuals listed in the Ahnentafel chart
are ancestors of the Base Rin#.

The descendant chart is printed listing the descendant, birth date
and place, death date and place, and then the same data for the spouse.
If there is a spouse, the marriage data is placed under the spouse.

Each generation is numbered.   The relationship of the Descendant
and Ancestor is given at the end of the chart.

The descendant chart is printed at 12 cpi and 8 lpi for both
printers.  The anentafel is printed at 12 cpi for the dot matrix
and 13 cpi for the Laser printer.  If the 12 cpi setting on the dot
matrix causes line wrap on longer lines then change the manual setting
on your printer to condensed print.  If both printers have problems
with wrapping on the longer lines then it is suggested that you
use NAMCLEAN20 and change all full state names to the two letter
abbreviations to shorten the lines.

AHNENTAFEL:

The Ahnentafel chart is based upon the base RIN. Ahnentafel numbers
are printed for easy identification of family lines.  Birth date
and place, death date and place are also listed if known.  The
number of individuals contained in a completely full 52 generation
chart would be limited to 9,007,199,254,000,000+ individuals which is
like the RIN numbers, far above what PAF will handle.  Also 52
generations will take you back to approx. 500 AD before reaching
this limiting ahnentafel number so should cause no serious
problems for most database.

If all the lines in your PAF data pedigree chart are full, PAF
will only hold 16 generations.

Basically, giving yourself an ahnentafel number of 1 and then
double it for each generation.  This would give your father a
number of 2, your paternal grandfather a number of 4, his father a
number of 8, etc.  The wife of an individual is given his number
plus 1.  Therefore your mother would be  number 3, your maternal
grandfather would be 6, etc.  This relationship can be seen in
the chart printed by AHNDES.EXE and is necessary to determine
the family lines from the chart.

PRINTING/SAVING:

Both the Descent Chart and the Ahnentafel can be either output
to the printer or saved to disk file.  If output is to the
printer it is paginated with left border sufficient for binding.
If output to a disk file, no margins or pagination is provided.
This must be accomplished by printing with your text editor or
word processor.  The Ahnentafel must be printed with print
CPI greater than 10.  Current printing is set at 12 CPI but if
printed with text editor then either 12, 15, or 17 would
suffice.  Descent chart will print satisfactorily with 10 CPI.
The disk file will be saved in the PAF data directory.  The descent
chart will be named DESDATnn.DAT and the Ahnentafel will be
saved as AHNTAFnn.DAT.  The numbering system will be as explained
below for the Focus File.

A list of the RIN#s on the Descent Chart and on the Ahnentafel
can be saved in either an ASCII text file or in a PAF Focus file.
These files are saved in the PAF Data directory and are numbered
sequentially.  Then name you enter for the FOCUS file is placed
internally in the FOCUS file and will not appear on your drive
directory.  FOCUS files are named IFOCUSnn.DAT (the 'nn' designating
a number).  If a file of that number is already in existence then
the file is automatically given the next number.  Up to 99 Focus
files may be saved.  The ASCII Text file is named DECLSTnn.DAT
for the Descendant chart and AHNLSTnn.DAT for the Ahnentafel.  These
follow the same numbering system as the Focus file.


HISTORY:

Version 3.0  makes major changes in the method of handling the
index file.  The index files is no longer retained but is created
new for each run.  On the descent charts the creation of the
index file is terminated as soon as the ancestor is located.
If there are cousin marriages creating multiple descent lines
then the descent chart created will follow the descent line which
appears to the left on a pedigree chart.  To print charts for
these additional lines, find the marriage where the lines rejoin.
Temporarily remove from the family the spouse that is NOT in the
line you want. Now run a new decendant chart using the same
descendant and ancestor.  The new path will be followed.  These
marriages can be identified by tracing these line on the Ahnentafel.
On the ahnentafel chart the entire database is indexed for the
number of generations selected.

A disk file of the RIN#s in both the Descent chart and the
Ahnentafel can now be saved to either a ASCII text file or to
a Focus file.  The Focus file can be used as input file for
a GEDCOM of this group of RIN#s.  Both the ASCII text file and
the Focus file can be used as input to PAFSPLIT by Ann Turner
for separating this group of RIN#s from the main database.

Version 2.3 extends the accepted years for dates to 2010.

Version 2.2 made several minor changes effecting printing of reports.

Version 2.1 adds the fourth place field to the event entries.
Adds the option of including or excluding the RIN #s in the
charts.  Eliminates the Marr: line on the descent chart if there
is no marriage date found.  Changes the printer code for 12 cpi
to accommodate more printer types.  If code does not match your
printer, then the default of 10 cpi will be printed.  Substitutes
Christening and Burial dates/places if Birth and Death dates are not
found.  Reduces the lines/page by two to help accommodate single sheet
feed printers.  Total lines in one page should not now exceed 60 but
under some circumstance still may.  If problems still occur here it
might help to disable your paper out sensor.

Version 2.0 corrects program crash on Descent charts when
the Birth, Death, or Marriage date field is completely filled
with the longest date entry possible in the family records.
Example of a full date field:    Abt 22 Jul 1940/1941

Version 1.9 corrects the failure to recognize descendants in
multiple lines due to cousin marriages.  Descendants in all
lines created by cousin marriages are now recognized and listed
in their descent chart.  Only one line is followed if the ancestor
is common to both lines and the descendant is a descendant of
the cousin marriage.

In the case of multiple lines due to cousin marriages, the line
followed in a descent chart is the line down from that ancestor
that falls furtherest to the right on a pedigree chart.

To obtain descendant charts of the other multiple lines, use the
cousins of the marriage as base rins and run their descendant
charts separately.  Then if necessary, use that member of the
marriage as the ancestor and enter the desired rin as descendant
creating the continuation of the descendant chart.

Requirement for re-entering the location of the database is
deleted for additional runs on the same database.

Version 1.8 improved algorithm reduces index creation time.
Offers option of limited number of generations.  Maximum still
remains at 52.

Version 1.5 corrects bug in Version 1.4 mod on proper selection
of wife for descent in multiple marriages.

Version 1.4 corrects the following problems encountered in earlier
versions:

    1.  Improper selection of wife in multiple marriages.
        The ancestral wife no longer has to be listed in PAF
        as the first spouse in multiple marriages.

    2.  No more hang ups if there is no husband in the marriage.
        The line now will continue with the ancestors of the
        wife.

    3.  Correct RIN for the spouse of the first generation
        individual in the Anentafel chart is now displayed.

    4.  Elimination of garbage display for the first generation
        individual if there was no spouse.

    5.  Reduced memory requirement for program operation.  Less
        problems with memory on some machines during the sort
        phase.

    6.  Index file is now in the same directory as the PAF data
        and AHNDES.EXE can be run from any drive:\directory.

AHNDES30.EXE is released as shareware.  A small donation of
$5.00 to the below address, it would be appreciated.  AHNDES.EXE
may be copied and distributed in its original package with no
charges for the software.  This Text file must accompany the
AHNDES.EXE file in any distribution package.

This can be mail ordered from the author by sending $5.00 + $2.50
S&H to the address below.

Please use and enjoy this program.

Thank you,

Jack J. Chandler
812 Vermillion Dr.
Henderson, NV  89015

PH 702-565-3158
