Log File

 
Log File
The Log files lists information about the input file. You use the View Log File(s) command to view the Log file, and it is opened in your default text file viewer,
 
Behold does a lot of checking of the data for non-standard GEDCOM structures and for data problems that need your correction. The next page of this User Guide contains a complete list of the messages Behold can generate in the Log file.
 
1

Filename

1. Filename
The log file by default will be the GEDCOM file name with ".log" appended on the end. This makes it easy to identify the log file for any GEDCOM file and it will follow the GEDCOM file in a Windows Explorer alphabetical listing of a directory.
 
2

Preamble

2. Preamble
Preamble is a great word to mean the beginning of a file. The log file starts with "how", "who" and "when", and then goes into "what" and gives info about the "what".
 
3

Input Messages

3. Input Messages
Behold will list everything that it finds that is not quite right in the input file. Each message consists of:
 
  1. The line number in the GEDCOM file followed by a colon. e.g. 246:
     
  2. The GEDCOM line in question, e.g. 2 MAP
     
  3. A short form of the message, preceeded by two asterisks to set it off, e.g. ** Tag NotAdded 551
     
  4. The number of occurrences so far of this message, in parenthesis preceeded by #, e.g.: (#1)
     
  5. The long form of the message.
 
Many messages are simply incorrect GEDCOM syntax that Behold understands and interprets properly. These messages are included in the log file to let you know what is non-standard about the GEDCOM file, because other programs may not be able to read them. Because of this, you should be aware that you may lose this data if you read this into other programs.
 
Behold understands many exceptions and extensions to GEDCOM. Behold will read all of your data, and is unaffected by the problems in the file that are listed.
 
4

Data Problems

 
A special type of input message is a data problem. If it occurs at a specific line, the line number and line will be given. But some are not determined until all data is loaded. In that case, details of the problem will first be given which will often include Tag IDs and names to allow you to track it down in your data.
 
The short message will always start with: ** Data Problem:
 
The long message will include a recommendation of what needs to be done to fix the problem.
 
Behold does not yet do sanity checking of dates, i.e. too young or too old at birth of child. This will be added in a future version.
 
5

The Rest Of It

Following the messages are several other summaries:
 
  1. Header  Information, e.g.:

       
     
  2. Summary of GEDCOM Tags and the number of each, divided into 3 sections: Records, Pointers and Data Tags, e.g.:

       
        etc...
       
     
  3. Processing Time, e.g.:

       
     
  4. And finally a summary of all the GEDCOM messages, with the counts of each message in parenthesis. This summary is also included in the File Information of the Everything Report, e.g.: