I’m still making my last few changes to the event sorting. I have to put the children in birthdate order, and the spouses into marriage order. I’ll be embedding them into the right place (date-wise) amongst all the events of an individual. Doing so just makes adding the consistency checking very natural to implement right now - rather than trying to come back to it later. I don’t expect it to take too long.

I’ve worked 17 years to get to this point. What’s another week or two, especially if it adds a very important and needed feature?

Louis

You’ll be interested to know that as a result of your earlier email to me, I reinvestigated consistency checking. With the addition of true date parsing and my implementation of that in version 1.0.1, this is now quite possible, and the setup of Behold makes it rather do-able. If I can squeeze it in in the next week or two, I’ll do it prior to 1.5, and then Behold will have comprehensive error checking on all fronts. To be different than all programs yet again, those consistency checks will be added in the Everything Report, right beside the inconsistent data.

Not only that, but as part of my 1.5 export to GEDCOM, I will need to be 100% sure that the GEDCOM I export is true 5.5.1. (It’s got to be 5.5.1 and not 5.5 because 5.5 does not allow UTF8 Unicode). I currently only do loose input checking. But my writing of the date parser is easily extendable to writing of a full comprehensive GEDCOM parser. I’ll be able to detect “all” GEDCOM problems instead of just many (including lengths of fields) and then do my best to change them into the closest fully-GEDCOM-compliant equivalent.

To me, this is very exciting. Behold’s error checking will be very complete, and then out of the way as I develop my native file format.

Louis