John, I was unaware of this as well.
I hope Darrin will fix it or is there an easy was to change the gedcom contents before importing into TNG? I am always frustrated when creating a gedcom in Legacy for "Changed" persons, and then importing that (appending to an existing database) into TNG ALWAYS screws up the family group Legacy has a check to add Parents and Spouses and Children, BUT what about SIBLINGS!! so in TNG the FAMC gets replaced with only those included in the gedcom. so frustrating..... Let me know what I can do to help, as I am sure there are many Legacy Users importing into TNG. Thanks Jay 1FamilyTree.com On Wed, Mar 25, 2015 at 1:49 PM, John B. Lisle <leg...@johnlisle.com> wrote: > Hi, > > A user recently reported to me that Child Status attributes, such as > Stillborn, Twin, Adopted, etc., were not being imported into his TNG > web site from a Legacy Gedcom file. > > Analysis shows that Legacy is exporting the Child Status in Gedcom, > and can import those Legacy Gedcoms properly back into in Legacy. But > the TNG web publishing application that many Legacy users use does > not import the tag that Legacy uses to report Child Status. (Legacy > currently exports it as an attribute of the child in the family structure.) > > --> IE, none of your Child Status attributes have EVER been imported > into TNG. Maybe this OK with you? Maybe you have never noticed? > > Further analysis shows that Legacy's approach to Child Status seems > to be unique among the major genealogy products and, although the > best (as far as I am concerned) actually, may not be optimal. In > reality, there is no consistency in how various products implement > Child Status attributes, if they handle them at all. > > Consequently, the TNG developer has less incentive to provide the fix > for this mis-match with Legacy. > > As this has been a problem for 10+ years with, supposedly, only > myself and one other user expressing concern over this to Legacy, I > would like to know if other users have seen this and would like to > see this resolved. Getting something resolved - and quickly - will > require having many folks second that this is an issue for them. > > --> Let me emphasize that this is not a Legacy bug. Legacy itself > works fine. This is a mis-match in the interface between two products. > > Also, do you know of any other programs where the current Child > Status implementation is causing a problem from Legacy Gedcoms? > > Thanks for listening, > > john. > nashua, new hampshire > > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > Archived messages from old mail server - before Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > Online technical support: http://support.legacyfamilytree.com > > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
