Don,
John's not talking about Child-Parent Relationship but Child Status.
I know that's confusing as Adopted is often entered as a Child Status
when it is really a Child-Parent relationship.
I understand that TNG has no problem with the Child-Parent relationship
Cathy

Don Quigley wrote:
>
> “Produce (Gedcom) File for Legacy” – with Child Status _not_ excluded.
>
> Donald Quigley
>
> Escondido, CA
>
> Quigley Doyle Family Tree
>
> http://www.donquigley.net
>
> *From:*CE WOOD [mailto:[email protected]]
> *Sent:* Wednesday, March 25, 2015 6:57 PM
> *To:* [email protected]
> *Subject:* RE: [LegacyUG] Issue with Gedcom Export of Child Status
>
> What GEDCOM version do you use?
>
>
> CE
>
> ------------------------------------------------------------------------
>
> From: [email protected] <mailto:[email protected]>
> To: [email protected]
> <mailto:[email protected]>
> Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status
> Date: Wed, 25 Mar 2015 18:05:02 -0700
>
> Hmmm. On my TNG website, the "child relationship" seems to show
> properly as the "Relationship" under a parent on a child's Personal
> Information page
>
> Donald Quigley
>
> Escondido, CA
>
> Quigley Doyle Family Tree
>
> http://www.donquigley.net
>
> -----Original Message-----
> From: John B. Lisle [mailto:[email protected]]
> Sent: Wednesday, March 25, 2015 1:49 PM
> To: [email protected]
> <mailto:[email protected]>
> Subject: [LegacyUG] Issue with Gedcom Export of Child Status
>
> 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/[email protected]/
> <http://www.mail-archive.com/legacyusergroup%40legacyusers.com/>
>
> Archived messages from old mail server - before Nov. 21 2009:
>
> http://www.mail-archive.com/[email protected]/
> <http://www.mail-archive.com/legacyusergroup%40legacyfamilytree.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/[email protected]/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> 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/[email protected]/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> 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/[email protected]/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/[email protected]/
> 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/[email protected]/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/[email protected]/

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

Reply via email to