Error Messages

All error messages shown in FamilyTreeFactory are written to be clearly understood.

Error messages for errors in Gedcom files

Some knowledge of data structures in Gedcom files may be necessary. An explanation of these structures follows. This only includes those elements with structural relevance, meaning those that are important for relationships between records.

Gedcom files save personal data in so-called individual records and relationship status information in so-called family records. The header of the files makes up a so-called head record. All rows begin with a hierarchy number. Rows with a hierarchy number of 0 open a new record. Rows with a hierarchy number >0 are a part of the previous row with the next smallest hierarchy number.

Relationship status information is indicated by cross-references from individual records to family records and vice versa. These corresponding references must both be present, according to the Gedcom standard. If one of these two references is not present, a serious data error will occur. FamilyTreeFactory will not be able to determine whether the single reference should be accepted or not.

The references from individual records to family records are as follows:

•	FAMS tag = partnership reference = reference to a family record, in which the person is a partner.

•	FAMC tag = child reference = reference to a family record, in which the person is a child.

In case of multiple partnerships, the individual record will contain multiple FAMS tags. The order of the tags should be chronological.

The references from family records to individual records are as follows:

•	HUSB tag = husband/father reference = reference to the individual record of the husband/father.

•	WIFE tag = wife/mother reference = reference to the individual record of the wife/mother.

•	CHIL tag = child reference = reference to the individual record of a child.

In case of multiple children, a family record will contain multiple CHIL tags. The order of the tags should be chronological according to the dates of birth of the children.

Data structure in Gedcom files

Header record	Meaning
0 HEAD	Record header
1 GEDC	Gedcom file
2 VERS 5.5	Gedcom-Standard Version 5.5
2 FORM LINEAGE-LINKED	Data are saved in lines
1 CHAR ANSEL	ANSEL character set

Individual Records	Meaning
0 @I123@ INDI	Record header
1 NAME John /Sampleman/	Name
1 FAMS @F45@	Partnership reference to family record F45, where I123 is a spouse (1st marriage)
1 FAMS @F46@	Partnership reference to family record F46, where I123 is a spouse (2nd marriage)
0 @I124@ INDI	Record header
1 NAME Erna /Samplewoman/	Name
1 FAMS @F45@	Partnership reference to family record F45, where I124 is a spouse (1st marriage)
0 @I125@ INDI	Record header
1 NAME Paul /Sampleman/	Name
1 FAMC @F45@	Child reference to family record F45, where I125 is the first child
0 @I127@ INDI	Record header
1 NAME Klara /Sampleman/	Name
1 FAMC @F45@	Child reference to family record F45, where I127 is the 2nd child
0 @I131@ INDI	Record header
1 NAME Maria /Samplelady/	Name
1 FAMS @F46@	Partnership reference to family record F46, where I131 is a spouse (1st marriage)

Family Records	Meaning
0 @F45@ FAM	Record header
1 HUSB @I123@	Husband/Father reference to individual record I123, the husband
1 WIFE @I124@	Wife/Mother reference to individual record I124, the wife
1 CHIL @I125@	Child reference to individual record I125, the 1st child
1 CHIL @I127@	Child reference to individual record I127, the 2nd child
0 @F46@ FAM	Record header
1 HUSB @I123@	Husband/Father reference to individual record I123, the husband
1 WIFE @I131@	Wife/Mother reference to individual record I131, the wife

The cross-linked relationship references are marked in color pairs.

Error messages for structural errors in Gedcom files

These error messages are noted in the log when a Gedcom file is opened.

Note: 'XRef' = cross-reference, refers to any given record reference in the form '@???@'.

If a reference to a record is present that does not exist in the Gedcom file, one of the following error messages will be displayed:

•	"Individual-Record XRef: Error: FAMS tag refers to a non-existent Family-Record XRef. Reference not accepted".

•	"Individual-Record XRef: Error: FAMC tag refers to a non-existent Family-Record XRef. Reference not accepted".

•	"Family-Record XRef: Error: HUSB tag refers to a non-existent Individual-Record XRef. Reference not accepted".

•	"Family-Record XRef: Error: WIFE tag refers to a non-existent Individual-Record XRef. Reference not accepted".

•	"Family-Record XRef: Error: CHIL tag refers to a non-existent Individual-Record XRef. Reference not accepted".

If a reference is only present in one of the two records, one of the following error messages will be displayed:

•	"Individual-Record XRef: Error: FAMS tag refers to Family-Record XRef, which is missing the corresponding HUSB tag".

•	"Individual-Record XRef: Error: FAMS tag refers to Family-Record XRef, which is missing the corresponding WIFE tag".

•	"Individual-Record XRef: Error: FAMC tag refers to Family-Record XRef, which is missing the corresponding CHIL tag".

•	"Family-Record XRef: Error: HUSB tag refers to Individual-Record XRef, which is missing the corresponding FAMS tag".

•	"Family-Record XRef: Error: WIFE tag refers to Individual-Record XRef, which is missing the corresponding FAMS tag".

•	"Family-Record XRef: Error: CHIL tag refers to Individual-Record XRef, which is missing the corresponding FAMC tag".

Error messages after the FamilyTreeFactory integrity check of records

The integrity check for FamilyTreeFactory records includes structural problems (one-sided references to relationships), data content (chronological order of events) and data formats (special saving formats of multi-line data fields and lists). The corresponding error messages clearly explain the errors that have been found, which can usually be corrected by modifying personal data.

If the integrity check reports structure errors, try to part the faulty relationships and then to connect them newly again. If this does not work for partnerships from one partner, try it from the other partner.