ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / GENEALOG / ACC50D1.ZIP / README.2ND < prev next >

Wrap

Text File | 1991-10-23 | 61.0 KB | 1,783 lines

************************************* * * * A C C E P T * * * * GENEALOGICAL RESEARCH PROGRAM * * * * Version 5.0 * * * ************************************* * * * USER MANUAL * * * ************************************* * * * SECTION 02. * * * * MODULE OPERATION * * * ************************************* * * * 01. NAMDBM MODULE / TEST FAMILIES * * 02. NAMDBM MODULE / VITAL DATA * * 03. NAMDBM MODULE / NEW PLACES * * 04. NAMDBM MODULE / AUX FILES * * 05. UPDATE MODULE * * 06. MARKER MODULE * * 07. MISCEL MODULES * * 08. * * 09. * * 10. * * 11. * * 12. * * 13. * * 14. * * 15. * * 16. * * 17. * * 18. * * 19. * * 20. * * 21. * * 22. * * 23. * * 24. * * 25. * * * ************************************* 1991OC23 C&SC Inc. 1 02.01 ******************************************************************* **** N A M D B M M O D U L E - T E S T F A M I L I E S **** ******************************************************************* ENTRY NOTES: ************ Be sure you have completed the Computer and Program Setups in the previous section of this manual. Entering the following test families will exercise most of the program features for you. In fact this is the worst intermarriage web we could dream up. (A Closed Genetic Pool) In the following test families the two names above the line are the Father and the Mother. The names below are the children. There can be any number of children but for this exercise there will only be two. The numbers to the right are the I.D. Numbers that will be assigned automatically after entry. This is a Base 32 (DUHEX) Numbering system. It is Alpha/Numeric. All the vowells except E have been removed to avoid spelling all objectionable four letter words. It saves space in forms and files. Four characters will represent over a million numbers. Seven characters (as on PEDIGROUP sheet) represents over 34 billion. Ask us someday, why that many? Notice that we DO NOT enter any dates and places at present. This is to give the broadest possible search parameters to catch duplications. The N option (Name Only Query) can be used later in the place of the Q option (Full Query) to have the Query ignore dates and places. The surname will repeat during entry also unless the children changed the spelling. Several didn't like the way mom and dad spelled their names. You should enter the phrase "THIS IS A FICTICIOUS PERSON!" in the PRIMARY SOURCE field. This will prevent someone taking them as real at a later time if you forget to destroy the test files. That note will repeat itself each time you enter a new name if you do not delete it from the query screen. TEST FAMILIES: ************** SMYTHE JOHANNE 0001 SINCLAIR MARY AGASTA 0002 ----------------------------- SMYTHE JOHN SINCLAIR 0003-----* SMITH JAMES 0004 I I I 2 AARDVARK ARNIE 0005-----I-----* ZANZIBAR ZULA 0006-----I-----I-----* ----------------------------- I I I AARDVARK JANE 0007 I I I AARDVARK MAX B. 0008 I I I I I I I I I SMYTHE JOHN SINCLAIR 0003-----* I I JONES CATHERINE 0009 I I I ----------------------------- I I I SMITH MARY 000B I I I SMITH JOHN 000C I I I I I I I I I AARDVARK ARNIE 0005-----I-----* I TROUBLE JANE 000D I I I ----------------------------- I I I ARDVORK THOMAS 000E I I I ARDVORK HOWARD 000F I I I I I I I I I NEWFOLKS JOSEPH 000G I I I OLDFOLKS MARIA 000H-----I-----I-----I-----* ----------------------------- I I I I NEWFOLKS MAIRA 000J I I I I NEWFOLKS JOSEPH 000K I I I I I I I I I I I I AARDVARK ARNIE 0005-----I-----* I I PRETTY JANETTA 000L I I I I ----------------------------- I I I I AARDVORK MAXIE 000M I I I I AARDVORKE MINNIE 000N I I I I I I I I I I I I SMYTHE JOHN SINCLAIR 0003-----* I I I ZANZIBAR ZULA 0006-----------I-----* I ----------------------------- I I SMYTH HETHER 000P I I SMYTH BLYTHE 000Q I I I I I I SMITH JAMES 0004 I I XAVIAR MARY 000R I I ----------------------------- I I SMITH MARKUS 000S I I SMITHEY JACK 000T I I I I I I AARDVARK ARNIE 0005-----------* I OLDFOLKS MAIRA 000H-----------I-----------* ----------------------------- I AARDIVARK ARNEE 000V I AARDIVARK CHARITABLE 000W I I I ZANZIBAR ZULUE 000X I TROUBLE JUST PLAIN 000Y I ----------------------------- I ZANZIBAR BAD GUYE 000Z I 3 ZANZIBAR VUNDER KID 0010 I I I ARDVARK JOSE 0011 I SMARTT MAREE 0012 I ----------------------------- I AARDVARK ARNEE 0005-----------* AARDVARK SWEETIE 0013 ENTER THE FIRST TEST FAMILY: **************************** DISPL: SELECT/MAIN MENU Screen ENTER: ND <RET> DISPL: NAMDBM/TITLE Screen HIT: <Q> If you hit <N> instead of <Q> it will result in a Name Only Query. It will ignore any dates or places you have entered and thus give you an extremely broad search and still be able to enter some places. When entering children they may all be born in the same place. This allows you to enter only one place entry for the group sheet. DISPL: NAMDBM/QUERY Screen at the LAST NAME HIT: <UP ARROW> DISPL: PRI SOURCE --> ENTER: THIS IS A FICTICIOUS PERSON <RET> DISPL: LAST NAME --> ENTER: SMYTHE <RET> DISPL: FIRST NAME -> ENTER: JOHANNE <RET> HIT: <ESC> DISPL: *** CANDIDATES *** Screen - Person Not on File HIT: <RET> or <E> DISPL: NAMDBM/ENTRY Screen HIT: <H> DISPL: Is This a New Name (*Y/N) HIT: <RET> or <Y> DISPL: This will be HIS 1st marriage - Store Name (*Y/N) HIT: <RET> or <Y> 4 DISPL: ** ENTERED ** Screen - JOHANNE entered as Father - ID#0000001 HIT: <Q> DISPL: NAMDBM/QUERY Screen at the LAST NAME --> HIT: </> ENTER: SINCLAIR <RET> DISPL: FIRST NAME -> ENTER: MARY <RET> DISPL: MIDDLE NAME -> ENTER: AGASTA <RET> HIT: <ESC> DISPL: *** CANDIDATES *** Screen - Person Not on File HIT: <RET> or <E> DISPL: NAMDBM/ENTRY Screen HIT: <RET> or <N> DISPL: Is This a New Name (*Y/N) HIT: <RET> or <Y> DISPL: This will be HER 1st marriage - Store Name (*Y/N) HIT: <RET> or <Y> DISPL: ** ENTERED ** Screen - MARY entered as Mother - ID#0000002 HIT: <Q> DISPL: NAMDBM/QUERY Screen at the LAST NAME --> - Note it has returned HIT: <RET> DISPL: FIRST NAME -> ENTER: JOHN <RET> DISPL: MIDDLE NAME -> ENTER: SINCLAIR <RET> HIT: <ESC> DISPL: *** CANDIDATES *** Screen - Person Not on File HIT: <RET> or <E> DISPL: NAMDBM/ENTRY Screen 5 HIT: <RET> or <N> DISPL: Is This a New Name (*Y/N) HIT: <RET> or <Y> DISPL: Store Name (*Y/N) HIT: <RET> or <Y> DISPL: ** ENTERED ** Screen - JOHN entered as Child - ID#0000003 HIT: <Q> DISPL: NAMDBM/QUERY Screen at the LAST NAME --> ENTER: SMITH <RET> DISPL: FIRST NAME -> ENTER: JAMES <RET> HIT: <ESC> DISPL: *** CANDIDATES *** Screen - Person Not on File HIT: <RET> or <E> DISPL: NAMDBM/ENTRY Screen HIT: <RET> or <N> DISPL: Is This a New Name (*Y/N) HIT: <RET> or <Y> DISPL: Store Name (*Y/N) HIT: <RET> or <Y> DISPL: ** ENTERED ** Screen - JAMES entered as Child - ID#0000004 VIEW THE FIRST TEST FAMILY: *************************** This routine allows you to view the vital record for each family member and see if the links are correct. Later it will be used to fill in the rest of the vital data via the EDIT Mode. HIT: <V> DISPL: NAMDBM/VITAL DATA Screen - Persons ID# ? ENTER: 1 <RET> DISPL: NAMDBM/VITAL DATA Screen #1 HIT: <V> 6 DISPL: Persons ID# 0001? - Old ID# Remains HIT: 2 <RET> DISPL: NAMDBM/VITAL DATA Screen #1 HIT: <V> DISPL: Persons ID# 0002? HIT: 3 <RET> DISPL: NAMDBM/VITAL DATA Screen #1 HIT: <U> DISPL: USER DATA Screen #2 (User defined data) HIT: <V> DISPL: NAMDBM/VITAL DATA Screen #1 ENTER AND VIEW THE REMAINING TEST FAMILIES: ******************************************* You use the exact same procedure to enter the remaining test families as you did to enter the first test family. In the case of multiple marriages the computer will keep a special linking file that will allow the entry of any number of marriages for one person. When you come to a person that has entered before as a child or another marriage be careful to enter the OLD ID# TESFAM\EXTEND FILE: ******************* After you finished entering and viewing all these mixed up families you should study the multiple marriage linking file called EXTEND. HIT: <X> (To return to the Main Menu DISPL: ACCEPT/MAIN MENU Screen ENTER: EX <RET> (To select EDIT EXTENTION FILE) EDITEX/MENU Screen This file ties the multiple marriage nightmare together for you. Be sure printer is on-line HIT: <1> (To Print Extend File) REC# SPOU KID1 NEXT ---- ---- ---- ---- 7 0001 000D 000E 0002 <-- ARNIE AARDVARK(0005) / JANE TROUBLE(000D) 0002 000L 000M 0005 <-- ARNIE AARDVARK(0005) / JANETTA PRETTY(000L) 0003 0006 000P .... <-- JOHN S. SMYTHE(0003) / ZULA ZANZIBAR(0006) 0004 0003 000P .... <-- ZULA ZANZIBAR(0006) / JOHN S. SMYTHE(0003) 0005 000H 000V .... <-- ARNIE AARDVARK(0005) / MAIRA OLDFOLKS(000H) 0006 0005 000V .... <-- MAIRA OLDFOLKS(000H) / ARNIE AARDVARK(0005) Your EXTEND File should look exactly like this one at this time. Ignore the marriage dates and places. If it does not you should try your hand at editing this file via #6 The Edit Marriage Extend To really clarify this little nightmare: HIT: <3> (To Display Marriages) EDITEX/DISPLAY MARR Screen - Persons ID# HIT: <5> <RET> (To Display Arnie Aardvark marriages) Displays the Pointers that are in Arnie's POINTS Record HIT: <RET> Displays the Pointers that are in EXTEND Record #1 HIT: <RET> (Until you reach the end) Play around with this EDITEX (Edit Extend File) Routine until you begin to understand its structure so you can edit it if some problems crop up later. HIT: <X> (To return to the Main Menu 02.02 ******************************************************************* ******* N A M D B M M O D U L E - V I T A L D A T A ******* ******************************************************************* ENTERING AND QUERYING THE DATES: ******************************** DISPL: SELECT/MAIN MENU Screen ENTER: ND <RET> DISPL: NAMDBM/TITLE Screen HIT: <V> DISPL: NAMDBM/VITAL DATA Screen - Persons ID# ? ENTER: 1 <RET> DISPL: NAMDBM/VITAL DATA Screen #1 8 You will notice that no dates and maybe only a few places have been entered yet. This is because your want to start all queries as broad as possible. If you get too many records then you start narrowing them down by using the Places and Dates. (Space/Time Variables). The DATE/TIME Format we will use was developed for this program almost ten years ago. It was included in all the copyrights since that time. All dates will be entered as: .1990MR23 JA=JAN FE=FEB MR=MAR AP=APR MY=MAY JE=JUN JL=JUL AU=AUG SE=SEP OC=OCT NO=NOV DE=DEC SEE: DATING SYSTEM 03.04 For more details. HIT: <F1> DISPL: NAMDBM/EDIT VITAL HIT: <RET> Twice DISPL: BIRTH DATE --> ENTER: .1930MR21 <RET> Do not enter the 1 over the top of the first period. You can continue in the same manner and enter dates for every person if you wish. HIT: <ESC> To record the change HIT: <Q> DISPL: NAMDBM/QUERY Screen at the LAST NAME --> ENTER: . (THIS WILL QUERY ALL NAMES) HIT: <DOWN ARROW> Three times DISPL: DATE/PLACE ->BD Indicates Date #1 and Place #1 is BIRTH Date #2 and Place #2 is DEATH Query searches 5 Dates but only 2 at one time. Do not change this if this is your first run HIT: <DWN ARROW> DISPL: DATE #1 (In this case it is Birth Date) ENTER: 1930MR31 <RET> You can query on any part of the dates in the following format: Include the periods. 9 1930.... Select only 1930 records. (BIRTH, DEATH ETC.) 1930MR.. Select only 1930MR records 1930MR21 Select only 1930MR21 records 1930--25 Select from 1905 to 1955 inclusive records HIT: <ESC> To execute query DISPL: *** CANDIDATES *** Screen - Shows person with that birtdate. You should play this game with dates until you feel comfortable. ENTERING PLACE CODES: ********************* This procedure shows you how to generate and enter Place Codes into each persons record. (They are also refered to as Place Abbreviations) The Place Names (Full Spellout) do not have to be entered until later. HIT: <V> DISPL: NAMDBM/VITAL DATA Screen - Persons ID# ? HIT: <1> <RET> DISPL: NAMDBM/VITAL DATA Screen #1 The PLACE CODE Format we will use was developed for this program almost ten years ago. It was included in all the copyrights since that time. All places will be entered as: USCTNHWH (This is the Place Code) This reads: UNITED STATES, CONNECTICUT, NEW HAVEN, WEST HAVEN SEE: PLACE SYSTEM 03.05 For more details. You will have to generate the Place Codes for the places you are using. The U.S.Postal Service uses a two character Code system for each state. It may be best for now to use theirs. They will change someday. Texas is worst when it comes to generating a two char code for counties. The disadvantage of having to generate Place Codes is far out weighed by being able to search each place on four levels. A fairly complete Place Code file for the world is available. HIT: <F1> DISPL: NAMDBM/EDIT VITAL HIT: <RET> Until you get to BIRTH PLACE > ENTER: USCTNHWH <RET> (Place Code) 10 DISPL: NOT ON FILE YET (This will display place later) HIT: <ESC> To record the change At this point you should enter several different place codes for several different names. Be sure to jot them down as you go along. ENTERING PLACE NAMES: ********************* FILES: PLACES (PLACE File) PLADEX (PLACe InDEX FILE) LOCATION: C:\TESFAM (All xxxFAM Directories) This ROUTINE lets you enter PLACE NAMES (Full Spellouts) into a table or file called PLACES. It has a search index called PLADEX. DISPL: NAMDBM/EDIT VITAL HIT: <A> (AUX FILES) DISPL: NAMDBM/AUX NOTE Screen (You really should read it) HIT: <RET> DISPL: NAMDBM/AUX MENU Screen #2 thru #9 are called Auxiliary Handbook files (AUXHB2 - AUXHB9) SEE: AUXILIARY HANDBOOK FILES 02. #1 Places (Entry/Edit) interacts with other modules and is not the same as the AUXHB files which are described below. HIT: <1> (Places Entry/Edit) DISPL: NAMDBM/PLACE EDIT Screen - SELECTION HIT: <3> (Add a Place Record) DISPL: NAMDBM/ADD PLACE - Record Number --> This is the computer generated number of record you are now entering. DISPL: Abbreviation ---> ........ ? ENTER: USCTNHWH <RET> (Place Code)(2 Char/Area) DISPL: County ---------> .... ? ENTER: NEWH <RET> (4 Char County) DISPL: State ----------> .... ? ENTER: CONN <RET> (4 Char State) DISPL: Latitude -------> 00X00'00 ? (SEE: PLACE SYSTEM 03.05) 11 HIT: <RET> DISPL: Longitude ------> 000Y00'00 ? HIT: <RET> DISPL: Established ----> DATUNK ? HIT: <RET> (This puts DATUNK in this position for now) DISPL: Full Name ------> ENTER: West Haven, New Haven, Connecticut, U.S.A. <RET> This must be entered as it will appear on the reports i.e. Town, County, State and Country. Country is optional. If you don't know the Town you must enter: ' New Haven, , Connecticut The commas tell the computer the County is missing. The Place Code is in reverse order for search purposes. Be sure to use the comma with a space after it to separate each area. HIT: <RET> (For next entry) At this point you should enter all the Place Names that you generated codes for previously. HIT: <X> (Exit to Place Edit Menu) DISPL: NAMDBM/PLACE EDIT Screen HIT: <7> (Merge New Place Records) DISPL: NAMDBM/MERGE PLACES Screen - Now Merging Places DISPL: NAMDBM/PLACE EDIT Screen HIT: <5> (List Place File to Screen) DISPL: Present Place Listing HIT: <6> (List Code Definitions) DISPL: NAMDBM/PLACE CODES - Place Code ? If you enter: US...... it lists all States in US you are using If you enter: USCT.... it lists all Counties in CT you are using If you enter: USCTNH.. it lists all Towns in NH County you are using Before this will work however you must enter the following: 12 Enter US...... as , , , United States or as ...., ...., ...., United States Enter USCT.... as , , Connecticut, United States or as ...., ...., Connecticut, United States Enter USCTNH.. as , New Haven, Connecticut, United States or as ...., New Haven, Connecticut, United States United States is optional. QUERYING PLACES: **************** HIT: <Q> DISPL: NAMDBM/QUERY Screen at the LAST NAME --> ENTER: . (THIS WILL QUERY ALL NAMES) HIT: <DOWN ARROW> Three times DISPL: DATE/PLACE ->BD Indicates Date #1 and Place #1 is BIRTH Date #2 and Place #2 is DEATH Query searches 5 Places but only 2 at one time. Do not change this if this is your first run. HIT: <DWN ARROW> Twice DISPL: PLACE #1 (In this case it is Birth Place) ENTER: USCTNHWH <RET> HIT: <ESC> To execute query DISPL: *** CANDIDATES *** Screen - Shows person with that birthplace. You can query on any part in the following format: (Include periods) US...... Select all UNITED STATES Records (Including Connecticut) USCT.... Select all CONNECTICUT Records (Including New Haven County) USCTNH.. Select all NEW HAVEN COUNTY Records (Including West Haven) USCTNHWH Select all WEST HAVEN TOWNSHIP Records HIT: <ESC> To execute query You should play this game with places until you feel comfortable. UNITED STATES ABBREVIATIONS: **************************** 13 ALABAMA ------ AL LOUISIANA ---- LA PUERTO RICO -- PR ALASKA ------- AK MAINE -------- ME RHODE ISLAND - RI ARIZONA ------ AZ MARYLAND ----- MD SOUTH CAROLINA SC ARKANSAS ----- AR MASSACHUSETTS MA SOUTH DAKOTA - SD CALIFORNIA --- CA MICHIGAN ----- MI TENNESSEE ---- TN CANAL ZONE --- CZ MINNESOTA ---- MN TEXAS -------- TX COLORADO ----- CO MISSISSIPPI -- MS UTAH --------- UT CONNECTICUT -- CT MONTANA ------ MT VERMONT ------ VT DELAWARE ----- DE NEBRASKA ----- NE VIRGINIA ----- VA DST COLUMBIA - DC NEVADA ------- NV VIRGIN ISLANDS VI FLORIDA ------ FL NEW HAMPSHIRE NH WASHINGTON --- WA GEORGIA ------ GA NEW JERSEY --- NJ WEST VIRGINIA WV GUAM --------- GU NEW MEXICO --- NM WISCONSIN ---- WI HAWAII ------- HI NEW YORK ----- NY WYOMING ------ WY IDAHO -------- ID NORTH CAROLINA NC ILLINOIS ----- IL NORTH DAKOTA - ND INDIANA ------ IN OHIO --------- OH IOWA --------- IA OKLAHOMA ----- OK KANSAS ------- KS OREGON ------- OR KENTUCKY ----- KY PENNSYLVANIA - PA MANUAL LINK ENTRY/EDIT: *********************** As you enter family groups into the computer the family relationship pointers are assigned automatically. These are the Natural Father & Mother, The 1st Spouse & the 1st Child of that spouse and the next youngest Sibling under that person. These can be added or changed later if they are missing at present. DISPL: *** CANDIDATES Screen *** HIT: <V> DISPL: VITAL REQUESTS Screen / Persons ID# ENTER: 0005 <R> DISPL: VITAL Screen for Arnie Aardvark FATHER : Ardvark Jose 0011 MOTHER : Smartt Marie 0012 CHILD1 : Aardvark Jane 0007 SIBLING: Aardvark Sweetie 0013 SPOUSE1: Zanzibar Zula 0006 HIT: <F1> To enter EDIT Mode HIT: <Up Arrow> To wrap around down to SIBLING HIT: </> To erase the field ENTER: 000D <R> DISPL: Trouble Jane This is not his sister so you can go back & change it again. HIT: <ESC> To enter the changes 14 SPECIAL NAME ENTRY CONVENTIONS: ******************************* There is space in the NAME FIELD for 33 Characters (30 Displayed). It is formatted as LAST NAME <SP> FIRST NAME <SP> MIDDLE NAME <SP><SP>... The LAST, FIRST, & MIDDLE Names MUST be Alpha Characters. They are indexed as Soundex values. Do not use numbers etc. They will fault out on the Soundexability Test. Put numbers in Roman Numerals 8th = VIII Do not have a space in front of the Last Name. It is permissable to use nick names (JAKE) etc. with parens in the place of the middle name. It will be indexed. It is permissable to use anything you want as a fourth name position: JONES John Paul *!&%$# It will only search on the first three names. Be sure there is a space after Paul. Royal Names can be quite complex. The following conventions are the best we could come up with. If you have some better suggestions let us know. Let's try Edmund "Crouchback" Plantagenet, Prince of England & Earl of Lancaster. Plantagenet is a Royal Family or Dynastic name and can be omitted. The Last or surname takes precedence over lesser titles such as Earl. Last Name First Middle ---------- ------ ------------ Prince.Eng Edmund (Crouchback) Abbreviate as much as possible without making it meaningless. K=King Q=Queen PRNC=Prince PRNCS=Princess DK=Duke Dchs=Duchess CNT=Count CNTS=Countess ERL=Earl SR=Sir LDY=Lady ENG=England SCOT=Scotland (When in doubt drop the vowells) There must be no space between such names as THE GOOD or THE CRUEL Enter such as T.GOOD or T.CRUEL or PRNC.ENG or DK.YORK Do not worry about upper case except as the first character of each name. Last Name FIRST NAME MIDDLE NAME -------------- ----------- ----------- K.Eng Henry VIII Prnc.Eng Edmund (Dk.Yrk) 15 Dk.Yrk Edward (No surname - use title) De.Mortimer Edmund (Erl.March) K.Castile.Leon Pedro.I (T.Cruel) LDS STATUS FIELD ENTRY: *********************** Every name record in the database has a 5 character field called STATUS. The Church of Jesus Christ of Latter-day Saints can use this to represent Temple Work Status. Position #1 M=Male F=Female Position #2 B=Baptism LDS Position #3 E=Endowment LDS Position #4 P=Sealed to Parents C=Born in Covenant Position #5 T=Temple Marriage The Non-LDS Users can use any set of status characters they wish here. These characters are searchable during a Query. If you only want to select male names for example then enter a M in position #1 TRUE Selection results if you enter a character in a position NOT TRUE Selection results if you enter X in a position. For the LDS User you can select all persons not baptised by putting an X in Position #2 for example. DON'T CARE Selection results if you enter a period in a position. If you don't care if a male or female is selected then enter a period in Position #1 The status field MUST have a period or some other character in each status position in both the records stored and the query. 02.04 ******************************************************************* ******** N A M D B M M O D U L E - A U X F I L E S ******** ******************************************************************* AUXILIARY HANDBOOK FILES SETUP AND OPERATION: ********************************************* FILES: AUXHB2 (AUXiliary HandBook #2) THRU AUXHB9 AUXMEN (AUXiliary MENu)(User can rebuild) 16 There are nine Active Handbook Files that are accessable while you are working within the NAMDBM module. They are like TSR (Terminate and Stay Ready) files but more quickly available. Other programs like PCTOOLS by Central Point Software inc. will also work. There is a set of active ones installed as samples. You can set up your own later as the need arises. Your sets can be stored in subdirectories based on country and or set numbers and copied into the active set. This can include unique menues for each set. For the first time through just use these sample files. Later you can build your own. You can also edit the AUX MENU to meet your own needs. FILE LOCATIONS: C:\TESFAM\AUXHB2-> - Active files (Samples at present) DIRECTORY LOC: C:\OURFAM\AUXDIR.GER\AUXHB2->9 - Inactive German files C:\OURFAM\AUXDIR.NOR\AUXHB2->9 - Inactive Norwegian C:\OURFAM\AUXDIR.001\AUXHB2->9 - Inactive Set #1 DISPL: *** CANDIDATES *** Screen ENTER: A <RET> DISPL: NAMDBM/AUX NOTE Screen HIT: <RET> DISPL: NAMDBM/AUX MENU Screen Places (#1) interacts with other modules and is not the same as the other AUXHB files. We will work later with this file. HIT: 2 (Political Ancestry in this case) DISPL: NAMDBM/HB2 Screen HIT: <SPACE> To scroll through screen HIT: <RET> To exit from file HIT: X (Exit to Main Menu) 02.05 ******************************************************************* ***************** U P D A T E M O D U L E ********************* ******************************************************************* UPDATE DESCRIPTION: ******************* FILES: NAMFIL (NAMes, Places & Dates for each person) POINTS (POINTers to persons Father, Mother, 1st Spouse etc) PRIDEX (PRImary inDEX to the NAMFIL records in Soundex) SECDEX (SECondary inDEX the NAMFIL records in Soundex) SESDEX (SESsion inDEX to the SESSION part of the NAMFIL) RESTOR (RESTORe file for NAMFIL/POINTS record links) 17 The NAMFIL/POINTS File Set is divided into two parts: The UPDATED Part and the SESSION Part. Every new name that you enter goes to the SESSION Part. REC# NAMFIL File POINTS File --------------------- --------------------- <---- UPDATED PART 0001 I I I I --------------------- --------------------- 0002 I I I I --------------------- --------------------- 0003 I I I I --------------------- --------------------- 0004 I I I I --------------------- --------------------- <---- SESSION PART 0005 I I I I --------------------- --------------------- 0006 I I I I --------------------- --------------------- The names in the UPDATED Part are sorted in Soundex order from a previous UPDATE Run. Only a few records are actually called from disk during a Query because of the Cascaded Soundex Index. The names in the SESSION Part are in the order which they were entered. Every record is called from disk during a Query. This is what we call a Brute Search. The reason this is done is to avoid doing a merge or index update every time a record is entered. If we did it would take well over the three second entry time limit we have set. When the two search methods take over three seconds combined then an UPDATE Run is required. On a 386 PC the Session Part can be up to a thousand before the update is needed. When the update program is run the Session Part is merged into the old updated part and new indexes are built. All of the update operations are done in a separate directory called OURUPD. The active files are not touched until the run is completed. If the disk were to crash during an update there would be a good chanch of losing all your new files. This way there is no chanch of it. The update is run via a batch file called OURUPD.BAT If you type it out you can see how the program is actually run. All these batch files enable you to set up your program for any number of databases. You will have to learn how to create your own batch files if your are going to get serious. RUNNING THE UPDATE: ******************* DISPL: MAIN MENU Screen 18 HIT: X To exit the MAIN MENU HIT: <RET> To exit the program DISPL: C:\ACCPRO> ENTER: C:\ACCPRO\OURFAM <RET> DISPL: BATCH RUN FOR OURFAM SETUP The old SUBST assignments, if any, are deleted and the new ones are assigned for OUR FAMILY Notice that OURUPD.BAT is copied over into the UP.BAT file. UP.BAT holds the update file handling for whatever database you are working with. It changes for each new database. ENTER: C:\ACCPRO\SE <RET> DISPL: MAIN MENU Screen ENTER: UP <RET> DISPL: UPDATE TITLE Screen HIT: <RET> DISPL: UPDATE MENU Screen HIT: <1> (To start the Update Run) If you crash during an update of an extremely large database this menu will allow you to return and resume at the crash point. Start with the one it crashed on. DISPL: The run sequence The program will stop when it is completed and allow you to print out the screen. HIT: <SHIFT><PRINT SCREEN> (Keep this printout for the record) If for some reason you do not want to transfer the new files into your active directory you may stop the program via <CTRL><BREAK> HIT: <RET> To transfer the new files into your active directory) At this time you should do a full backup of the OURFAM (or whatever) directory, date it, and store it away. Each time you do a Session File backup upon leaving the ND routine you should date it and store it with the last full backup. Please do this so I won't have to try and dry your tears! 02.06 ******************************************************************* 19 ***************** M A R K E R M O D U L E ********************* ******************************************************************* Whenever you make a list of something you usually place a check mark next to each item you have taken care of. The MARKER Module works in much the same way. The MARKER File itself is only one character (Byte) wide and is interchangable with other MARKER Files. The other MARKER Files can not have the name MARKER. Use such names as: MRKMINE, MRKHERS, MRKOLD, MRKNEW, MARKER.001 etc. Copy any of these files over into the MARKER file and they will become the ACTIVE MARKER File. Each record number in the active MARKER File corresponds to a record number in the POINTS File. Those in turn correspond to a persons ID#. They are parallel files. In effect what you are doing is selecting a persons record and then marking it with some character. The MARKER file allows you to print out groups of selected group sheets or pedigree sheets. It allows you to extract names from one database and build a new database. Because each routine in the MARKER Module is well documented on each sub-menu we will only make brief mention of each function. DISPL: C:\ ENTER: C:\CD ACCPRO <RET> DISPL: C:\ACCPRO> ENTER: SE <RET> DISPL: SELECT / MAIN MENU Screen ENTER: MK <RET> DISPL: MARKER / TITLE Screen HIT: <RET> DISPL: MARKER / MENU Screen A. Manually Mark By Individual ID# ********************************** This allows you to place any character mark you wish in the MARKER file. Because the MARKER file corresponds to a persons ID# it is the same as placing a mark next to that persons record. You will be asked for the type of mark you want to mark the name with and the persons ID#. The characters A thru Z are usually used but almost any character can be used. To change the mark you must exit and return. B. Manually Mark By Block of ID# ******************************** You can mark whole blocks of ID# by giving the starting and ending ID#. 20 You may want to mark and do something with the last 1000 names entered for example. C. Automatic Full Relative Marker ********************************* If you randomly select names and mark them there is is usually no common surname between them. This allows you to mark all the relatives associated with that person. The persons parents, adoption parents, spouses, parents of each spouse, children of each spouse and siblings. This allows you to build a new database for a friend of only the names he is interested in. D: Automatic Partial Relative Marker ************************************ If you mark everyone who has the same surname from a certain place and time then every child will cause their parents name to be marked over and over again if you use the Full Relative Marker routine (above) This Partial Relative Marker routine prevents this. E. Set The Active Marker File ***************************** This allows you to set the presently active MARKER file to a single selected mark. You may want a majority of records set to a certain mark. It would be easier to manually set the minority and automatically set the majority. Setting every one to a period clears the marker file. F. Display Marked Names In ID# Order ************************************ This allows you to make a listing of all the names you selected just for a check of errors. They are in ID# Order or order of entry. G. Display Marked Names in Soundex Order **************************************** This allows you to make a listing of all the names you selected just for a check of errors. They are in Soundx Order (Not Alpha) i.e. Maria, Mary, Maura etc all appear together. H. Build New Database From Marker File ************************************** This routine will extract marked records from the main database via the marker file and generate a new database from them. The resulting database will have new family ID#'s and pointers. The old ID#'s will appear in the primary source field together with the Source Database #. You must run the Full or Partial Relative Marker routine before running this routine. All the new files generated will be located in your family directory and will all start with the character Z i.e. ZNAMFIL, ZPOINTS etc. This allows you to copy them into a new directory by doing a COPY Z*. to \NEWDIR 21 I. Build New Place File For New Database **************************************** This will extract only those places that are to be used in the New Database. 1. Run the desired marker routine 2. Run the Build New Database Routine (H.) 3. Run this Build New Place File Routine (I.) 4. Copy all the files that start with a Z over into your new database directory. The new directory must have been loaded with all the starter files from the NEWFAM Directory first. 02.07 ******************************************************************* *********** M I S C E L L A N E O U S M O D U L E S *********** ******************************************************************* These modules are almost self explanatory via the menues and need only some brief notes. Any modules that are not described here are completely self explanatory and need no additional notes other than those in each menu. LP Large Pedigree Sheet *********************** This could have been made longer without any trouble other than you would need a stepladder to read the top lines and lay flat on the floor to read the bottom lines. You must use compressed print on your 80 column matrix printer to use this routine. The pieces are designed to be taped together. If you make one printout for each great grand parent and then one for yourself you can use your left half to point to the great grand parents. You can make a thousand large wall pedigrees if you like with some being pointers to the others. There is space within the first four generations to paste in photographs. If you only want to use the left half of each sheet in your wall display you can have photographs for everyone. Your kids are bound to install a picture of a Monkey or Blackbeard somewhere in your tree when you're not looking. Have fun. PS Pedigree to Screen ********************* If you print these screens out via the <Print Screen> key you can put two screens one one 8.5x11 sheet of paper. PG Pedigroup Sheet ****************** This form is my pride and joy and dates back 20 years. No genealogy form 22 presents as much as this one does in such a small space. It gives a persons roots, branches and history all in one. Because the pedigree is linear you can display your line all the way back to Adam (If you have one) without having to jump around through those endless fan out ancestral pedigree sheets. You are only interested in one line at a time anyway. To take off on any female line all you need do is reverse the two ID# numbers. When you enter the female first it results in a FEMALE GROUP SHEET. All your lines are female except one anyway. The female as far as display and searching is treated exactly the same as the male. Permission IS NOT GRANTED to use the PEDIGROUP format in any other program. The only thing we will give is a WO BE UPON anyone who tries! This also goes for the PLACE Format (USUTDVBN), the DATE Format (1991SE20), and the Base 32 (DUHEX) numbering system which we believe we were first to use about 15 years ago. LN Linked Name Sheet ******************** This gives a listing in: 1. Individual format 2. Individual + Spouse format 3. Individual + Spouse + Individuals Parents format 4. Individual + Spouse + Individuals Parents + individuals Children format The last format is a multiple display of mini-group sheet. This is an extremely compact way to mail out group sheets to someone interested in what you have. It's also nice to carry with you if you didn't by that little laptop yet. DS Descendant Sheet ******************* We have been using this descendant sheet format for several years now and to our knowledge no one has used it before. It can display any number of generations sideways and any number of families vertically. You may have to fold the vertical listing to the rear if it gets too long to hang on the wall. DU Dual Index Sheet ******************* This is kind of like having one phone book organized two ways. First by name and then by number. It prevents having two make two listings. If you send this to a friend or relative they can construct all the pedigrees and group sheets that you have just from this one sheet. They can see everything that you have in one small listing. It's great to send out to those thoughtful relatives that want a copy of everything you have. We have been using this one for several years now and to our knowledge this is the first time it has been used. 23 RL Relationship Generator ************************* This is the one I lost half my hair over. (My kids got the other half) Every user of your database has a different relationship to each individual stored than you do. This routine will generate a separate relationship file for each user. (RL00D5 for example) Each persons relation file will be activated when he starts to use the program. HI History File Generator ************************* In a way the History Files (HI0001 etc.) are the primary files and the relationship files such as NAMDBM, POINTS Etc. are the secondary files. Just about everyone starts with the Name, Birthdate/Place and the relationship that person has to others in the database. They want to construct pedigrees, group sheets etc. first, so we designed ACCEPT that way. We have linked the History file to the PEDIGROUP (PEDGRP) sheet and the NAMDBM/VITAL Screen to get the best of both approaches. The History file Generator takes all it can find in the NAMDBM & POINTS files and generates a starter history file for that person. From there on you can use your favorite editor to complete the History File. Be sure you save the file in ASCII so ACCEPT can use it. The History file is designed so it is FIXED Format towards the upper left and FREE format as you go towards the lower right. This must be maintained in order to incorporate some interesting future routines. There is a History File called HI0000 located in the NEWFAM Directory on Diskette #2. Follow this example as closely as you can. The three character codes on the left of each line make that item searchable when it is incorporated into a History Database in the near future. You must use the same codes. In HI0000 there are two lines with BRN. This indicates there is a conflict in the data and they come from different sources. In the future everyones history file will be merged into one extremely large database. Each line will be identified with the database # that line came from and the ID# used within the source database. The relationship pointers will be included. This will allow for some interesting retrieval schemes. This will also be done within your own database. XT Extract Groups ***************** This routine which is at present in the design stage. It may be a few months yet. This will enable you to extract group sheets from a Parish record so long as it is a Home Parish. (Honest) FF Filter a File **************** 24 This routine is in the development stage. (80% Finished) When you enter a name via the NAMDBM/QUERY routine an automatic check for duplication takes place. This prevents duplicate names being entered. In a linked file such as ACCEPT duplicate names can play havoc with name linking etc. This routine will work in much the same way except that it will take the names from the disk (other Session Files) and enter them only if no possible duplication candidates show up. If any show up they will not be entered but rather sent to the printer. This could go on for hours during a merge. After it is completed the user takes the printout and determines if those names should be entered or not. The user is the final arbitrator not the computer. Computers are much too dumb to play that role. EX Edit Extention File ********************** Without this file the number of children or spouses would be limited. Leaving empty spaces for the maximum number of spouses and children would take up a tremendous amount of space. This opens the program up to any number of children and any number of spouses and also the division of one persons children into sets according to his or her spouses. If you study the test families you entered you should be able to catch the file structure without too much trouble. The first marriage pointer is always in the POINTS Record that belongs to that person. All the other marriage pointers if any occur in the extend file together with the first child in that set. TE Tester Utilities ******************* Before you run an UPDATE you should run this routine. If you do not you may cause some problems. Almost anything can happen to your files and every effort has been made to protect the file integrity. There is one POINTS record and one NAMFIL record for each person in the database. They both are linked to eachother so that the two can act as if they are one record. NAMFIL deals more with searching and so is sorted in an UPDATE run. POINTS deals with family relation pointers and none of the records are relocated. The record location # is the same as the persons ID#. This prevents having to change pointers every time a record is moved around. Running test A. makes sure that these each record is part of the other. If it fails then use the U1 Utility routines to repair it. Each POINTS record contains pointers to the persons Father, Mother, 1st Spouse, 1st Child of the 1st Spouse and the persons Brother or Sister which was born just after the person. (SIB Down) These can be entered either automatically or manually via the NAMDBM/VITAL Screen. Running test B. makes sure none of those pointers are out of range. Every name has a Soundex value stored in the PRIDEX and SECDEX Indexes. You must not enter names as JONES JOHN 3rd as the poor computer doesn't 25 know what 3rd sounds like. Enter that in Roman Numerals. (III) Running test C. will check for that sort of thing. Be advised that you should run the DOS/CHKDSK program each time you turn on your computer. If lost clusters show up you can be in trouble if it happens to involve the ACCEPT files. CHKDSK only shows you a piece of the file that got bombed it does not repair it. It's like showing you some pages that just fell out of a book and then you have to decide which book it came from by looking at it. I don't know why they don't show which file the chunk came from. You can check the number of bytes in the NAMFIL file and then divide by 128 to find if the right number of records are there. You can also check the number of bytes in the POINTS file and then divide by 113 to see if you have the same number. These files must have the same number of records or do not use them. Fall back to your backups (which you better have) AS Append Session File ********************** This routine allows you to collect Session files from other databases or other family members that are using the same database as yours. It also allows you to restore your corrupted files by appending the last Session backup to the last complete UPDATE. This means you can have several hundred family members all working together without having to communicate over a network or modem. When the most active family member announces his Session file is need of an UPDATE then you as the Database Administrator tell every one to get out of the pool and send their session files in. They can ignore you if they have no names to submit. After the big merge you send the new updated database out to everyone and start all over again. Each person is then working against the latest database. These keeps down duplication to a minimum. AD Append a Database ******************** When a person receives a small database from another person using the ACCEPT program he can operate that new database in a stand alone mode or he can append it to his database if he feels the names should be included in his database. Collecting gravestone records can work in the same way. U1/U2 Utility Routines ********************** These are just a collection of small routines that may prove of some value if you get into trouble and want to do some file analysis and repair. PO Ponder ********* This is a collection of quotes on several subjects. They are included in ACCEPT to give you a mental break instead of a breakdown. 26 All S001 (SGC) quotes are included in the ACCEPT copyright & are not to be reproduced in any publication. If you want to step through every quote then enter N01, N02 ... at the prompt. TSR Terminate & Stay Ready Routines *********************************** The AUX Files can be viewed without stopping the NAMDBM program operation. This has been working for several years now. They do not have to save and restore the operating system environment so they are very fast. Recently several TSR's have become available. PCTOOLS is a good example. There is no conflict between ACCEPT and PCTOOLS. We have not tested any others. 27