Behold does lots of checking of your data. There are currently two types of messages:
-
Possible Data Problems are indications of something that is likely wrong in the data. You'll want to look at these and fix those needing to be fixed. They are shown in red and included in the Everything Report with your data where the error is. An example is:
An easy way to scan for these reported problems is to search for the double asterisk ** using the Find tool. If you want, you can change the ** to something else from the "Indicate data problems" item in the Organize Report page.
-
GEDCOM messages are non-standard constructs in the GEDCOM file. Behold can understand these, but other programs may not and those other programs may not read that data correctly from the GEDCOM file. Errors indicate invalid GEDCOM. Warnings are for valid constructs that may not be handled by many programs. These messages are listed in the log file along with the GEDCOM line the message pertains to and an explanation of what Behold does about the problem. An example is:
These messages provide the line number from the GEDCOM file, the GEDCOM line, the message, what Behold will do about it, and in parenthesis the message number of this type of message.
GEDCOM messages are also summarized in alphabetical order at the end of the File Information section near the end of the Everything Report. It lists each message type and the count of them. An example is:
Below is the list of all the data problems that Behold will report.
These are the Possible Data Problems:
Invalid Date:
**Calendar Roman is invalid
**Calendar unknown
**Date invalid
**Date >= second date
**Day > days in month
**Double year is not 1582 to 1918
**Double year is not consecutive
**Double year only valid with Gregorian calendar
**Double year must have 2 digits after slash
**Double year not allowed with B.C. dates
**Interpreted date must be followed by original in parenthesis
**Word after first date can only be "AND"
**Word after first date can only be "TO"
**Month must be in leap year
**Month invalid
**Month invalid for Hebrew calendar
**Month requires Hebrew calendar
**Month invalid for French calendar
**Month requires French calendar
**Month not allowed with B.C. dates
**Year is missing
**Year must be 3 or 4 digits
Date Consistency Checking:
**Occurs in the future
**Occurs before birth
**Occurs before marriage
**Occurs after marriage
**Occurs when old > 106
**Occurs before death
**Occurs after death
**Occurs too long after death
**Occurs before child-bearing age < 14
**Occurs after child-bearing age > 56
Self-Referential
**Ancestral loops need to be fixed
**Self-related as own
These are all the GEDCOM messages:
Error: This FAM record has HUSB and WIFE links that point to more than 2 people. Behold will accept them all.
Error: This FAM record has 2 HUSB links but GEDCOM only allows 1 HUSB link. Behold will accept them all.
Error: This FAM record has 2 WIFE links but GEDCOM only allows 1 WIFE link. Behold will accept them all.
Warning: This FAM record has CHIL records with birth dates out of order. Behold will reorder the child.
Warning: This INDI record has FAMS records with marriage dates out of order. Behold will reorder the marriage.
Warning: This INDI record has FAMS records with an inconsistent spouse death date. Behold will reorder the marriage.
Error: This line has no level number and/or no tag. Behold will ignore the line.
Error: A valid HEAD record is not at the start of this file. Behold will assume a HEAD record and continue reading.
Error: This record is referred to, but the record has not been defined. Behold will generate the record.
Error: A TRLR record is not at the end of this file. Behold will display what it found.
Error: An EOF record is not at the end of this file. Behold will display what it found.
Warning: This is a PAF date phrase. Behold will convert it to a NOTE.
Warning: This line contains one or more invalid Unicode character codes. Behold will read what it can.
Warning: This line contains invalid UTF-8 character codes. Behold will read what it can.
Warning: This line contains invalid UTF-8 character codes. Behold has replaced it with the Unicode "replacement character".
Warning: The character set is ANSEL, but the file has a Byte Order Mark. Behold will read the file as ANSEL.
Warning: The character set is UTF-8, but the file Byte Order Mark is missing. Behold will read the file as UTF-8.
Warning: The character set is UTF-8, but the file Byte Order Mark is not UTF-8. Behold will read the file as UTF-8.
Warning: The character set is Unicode, but the file Byte Order Mark is missing. Behold will read the file as Unicode.
Warning: The character set is not UTF-8 or Unicode, but the file has a Byte Order Mark. Behold will read the file in the character set specified by the Byte Order Mark.
Error: The character set is not specified in the header. The file has a a Byte Order Mark. Behold will read the file in the character set specified by the Byte Order Mark.
Error: The character set is not specified in the header. The file does not have a Byte Order Mark. Behold will read the file as ANSEL.
Warning: An illegal HEX 00 character is embedded in this line. Behold will display this character as a period.
Error: This link has already been defined. Behold will combine the data for these links.
Error: This record has already been defined. Behold will create a new record.
Error: There is extra data on the HEAD record. Behold will ignore it.
Error: This blank or invalid line is after the TRLR record. Behold will ignore it.
Error: There is extra data on this level 0 record. Behold will include and display this.
Error: This possibly valid line is after the TRLR record. Behold will attempt to process this.
Error: There is extra data on the TRLR record. Behold will ignore it.
Error: There should be no blank lines. Behold will ignore it.
Error: This line should not be indented. Behold will ignore the leading spaces and tabs.
Error: This line including the end of line delimiter is longer than 255 characters. Behold will read the entire line.
Error: This tag is missing a required link to a record (enclosed in "@"). Behold will treat any data value on the line as a data value for that tag.
Error: The note text should begin on the NOTE record. Behold will allow this.
Error: There is no place name on the PLAC tag. Behold will assign "unspecified".
Error: There is no record type on this level 0 record. Behold will include it as an unspecified record type.
Error: This FAM record has a HUSB or WIFE link that points to this INDI record, but the INDI record does not link back with a FAMS link. Behold will assign the link back.
Error: This FAM record is pointed to by a FAMS link in this INDI record but does not link back with a HUSB or WIFE link. Behold will assign the link back.
Error: This FAM record has a CHIL link that points to this INDI record, but the INDI record does not link back with a FAMC link. Behold will assign the link back.
Error: This FAM record is pointed to by a FAMC link in this INDI record but does not link back with a CHIL link. Behold will assign the link back.
Error: There is no space between the identifier and the tag. Behold will allow this. { In a GEDCOM 2.0 file gedr283.ged }
Error: This tag is not allowed to be used to define a GEDCOM level 0 record. Behold will allow this.
Error: Invalid GEDCOM tag. Behold will accept this tag.
Error: This tag is not a valid FTW TEXT tag. It is not a GEDCOM tag either. Behold will accept this tag.
Error: This tag is not a valid FTW TEXT tag, but it is a GEDCOM tag. Behold will accept this tag.
Error: Tag includes lowercase letters. Behold will try using the uppercase equivalent.
Warning: There is no text on the line to Concatenate. Behold will ignore this line.
Error: Tag was not added to GEDCOM until Version 5.4 Behold will accept this tag.
Error: Tag was not added to GEDCOM until Version 5.5 Behold will accept this tag.
Error: Tag was not added to GEDCOM until Version 5.5.1 Behold will accept this tag.
Error: Tag was removed from GEDCOM Version 5.3 and later. Behold will accept this tag.
Error: Tag was removed from GEDCOM Version 5.4 and later. Behold will accept this tag.
Error: Tag was removed from GEDCOM Version 5.5 and later. Behold will accept this tag.
Error: Tag was removed from GEDCOM Version 5.5.1. Behold will accept this tag.
Error: Tag was removed from GEDCOM Version 2.1. Behold will accept this tag.
Error: Invalid date. Behold understands the problem and is able to use this as a date.
Error: Invalid date. Behold will not use this as a date but just as text.
Error: This date value is longer than the 35 characters allowed in GEDCOM 5.5 or 5.5.1. Behold will accept this.
Error: This date value is longer than the 90 characters allowed in GEDCOM 5.4 and earlier. Behold will accept this.
Warning: This is a GEDCOM EL file that includes extensions to GEDCOM. Behold will correctly read this file including its extensions.
Warning: This version of GEDCOM is not the standard 5.5 or the de facto standard 5.5.1. Behold will correctly read this version of GEDCOM.
Warning: This an FTW TEXT file. It is not a GEDCOM file. The FTW tags will be mapped to their GEDCOM equivalent. Behold can read this file amd will map the FTW tags onto their GEDCOM equivalents. Most programs won''t.
Warning: This is a GEDCOM 2.0 file. It is very different than later GEDCOM files. Behold can read this file. Most programs won''t.
