3rd October 2014 at 4:00 pm #3481
I’m using the term “serious” maybe “obvious” was more appropriate. In any case, while kiwiTrees didn’t go bonkers, .GEDitCOM checks upon importing. Not sure if the error check would have caught them. Because, to me, the errors were so obvious but couldn’t be caught if I had no reason to look at the raw GEDCOM code for the record. Or, more correctly, catch the problem when I was. The date check I did in another offline genealogy application I played with. Lots of 01 SEPT 1900 where it wanted SEP — only a problem in that app as it’s not flexible. I had lots of BETW instead of BET — again, carried over from 2007 import but never caught.
11 CHAN >> the extra 1 caught from tag above; some had Level 3 tags before Level 2 tags; the one I couldn’t figure out was the Adoption one (I had the child adopted by the feather) but as it was only one record and couldn’t remember the other adoptees I had done correctly, just removed the extra tag.
This is just a guess that these contributed to the problem. I’m guessing that I’ll know for sure when you release next upgrade and all kiwiTrees files get replaced. Meaning it was me, not kiwiTrees, as I’m suspecting.
----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.