The Behold User Forum
Login to participate
  
Register   Lost ID/password?

Louis Kessler’s Behold Blog     The Behold User Forum

Forum Posts

  
Results 171 - 180 of 496 forum posts.   1253 blog entries.   740 blog comments.   2489 total.
171. 

Date validation - case sensitive - Forum post by brett in Report a Problem - 13 Apr 2012

I assume this applies to BET, ABt etc in that they can be Bet, bet etc but compared upper or lower cased. Brett
172. 

Date validation - case sensitive - Forum post by lkessler in Report a Problem - 13 Apr 2012

I think it simply means comparing for the purpose of interpreting its value. For a DATE value, I don't just compare the month-part to JAN, FEB, MAR,..., but I compare the uppercased value of the month-part to JAN, FEB, MAR,... For a TYPE value, I don't just compare the value to STILLBORN, but I compare the ...
173. 

Date validation - case sensitive - Forum post by brett in Report a Problem - 13 Apr 2012

So what does: values should be converted to all uppercase or all lowercase prior to comparing. actually mean? Is this when: 1. comparing two dates within a program, such as to work out age or 2. two supposedly identical GEDCOMs are compared for differences? If 1 above, how does a user know it is being done ...
174. 

Date validation - case sensitive - Forum post by lkessler in Report a Problem - 13 Apr 2012

Brett, See my blog post: How To Get A Developer To Fix A Bug. No, Tamura's correct. The statement: "values should be converted to all uppercase or all lowercase prior to comparing" means that aPR and aPr should be both changed to APR (if uppercase is used for comparison) or to apr (if lowercase is used for ...
175. 

Date validation - case sensitive - Forum post by brett in Report a Problem - 13 Apr 2012

Louis What do you make of Tamura Jone's comment (http://www.tamurajones.net/SiblingTortureTest.xhtml): None of these produced any errors or warnings, except Behold 1.04. Behold warned that the date 13 Apr 2012 is non-standard, and should be 13 APR 2012; the warning is that the abbrevation should be in ...
176. 

Version 1.0.5 (Life Events, Age at Events, Date Consistency Checking) - Forum post by brett in Questions and Answers - 9 Apr 2012

As usual, you have explained it to the degree it is no longer a thought to consider. Patiently waiting for that next version. Brett
177. 

Version 1.0.5 (Life Events, Age at Events, Date Consistency Checking) - Forum post by lkessler in Questions and Answers - 9 Apr 2012

Brett: Actually, no. The log file is associated with the GEDCOM file that is input. If you input 3 GEDCOMs into Behold at once, then 3 log files are produced. It is designed to tell you what import problems happen from the GEDCOM file. Once Behold has its own data file format, you will be reading from a .bhp ...
178. 

Version 1.0.5 (Life Events, Age at Events, Date Consistency Checking) - Forum post by brett in Questions and Answers - 9 Apr 2012

New: Add date consistency checking, that verifies event dates by comparing them with each person's birth and death dates and placing a message in the Everything Report next to the suspicious date. Louis Is it possible to display this in the log file as well as/instead of please. Brett
179. 

Probate - Forum post by lkessler in Report a Problem - 19 Mar 2012

cp: Thanks for telling me of this. No, I didn't even think of probate when I put the "events after death" together. I'll make that change and it will be in the next version of Behold. Louis
180. 

Probate - Forum post by cp in Report a Problem - 19 Mar 2012

I noticed your recent blog post regarding correct ordering of dates (eg burial after death - which behold does correctly out of the box). Can I note that probate also must happen after death (and almost always after burial/cremation - I can only think of very esoteric reasons that would invert that!). Behold, ...