Louis Kessler’s Behold Blog     The Behold User Forum

By enumerated list of choices, are you meaning 'controlled' as referred to in the specification: All controlled line_value choices should be considered as case insensitive. This means that the values should be converted to all uppercase or all lowercase prior to comparing. The terms UPPERCASE and UpperCase are ...

So does that warning greater than 255 comes as a result of an incorrect GEDCOM export?

Thanks Louis. My sympathy on your father's passing. Brett

Once editing and Behold file format, will the following result in truncation to conform to GEDCOM? 5908: 2 SOUR Citation Text: © Wiltshire Family History Society 2004 - Wiltshire Baptism CD (CDP1) Year : 1795 Date : MAY 18 Surname : BROWN Forename : STEPHEN Relationship : S ...

I am wondering if the action and warning: 248: 2 DATE 01 MAR ** Date Invalid (#1): This date does not conform to GEDCOM standards. could be changed to 248: 2 DATE 01 MAR ** Behold will change this to a date phrase by adding parenthesis.(#10): This date does not conform to GEDCOM standards.

We enter July in less than 5 hours. How are the following going please? Version 1.1, planned for May 2014. (Merge Family Info, Age at Events) Version 1.1.1, planned for June 2014. (Life Events) Version 1.1.2, planned for July 2014. (Who's Alive at Events)

Louis What version does Behold validate to? Is it the one in the GEDCOM file header (example below) or always 5.5? 1 GEDC 2 VERS 5.0

Dave I am running similar configuration to you. If you like, send me GEDCOM and I will see what it does here. I have had no problems on any size GEDCOM that loads into Behold. Brett

Push...push...push

Thanks for the explanation. It was the 'set up a bit differently than other programs' that tricked me.