On Tue, 22 Jun 2010 13:34:47 +1000, "John & Elizabeth Pethybridge" <[email protected]> wrote:
>If I look at the Incoming GED it has the "1st Alternative Name" as NICK & >the "2nd Alternative Name" as ALIA. >It appears that Legacy puts both in as GIVN of equal status, because when I >delete either of the Alternative Names in Legacy the other assumes the >Status & Position of "1st Alternative". Legacy exports them as GIVN & GIVN. > >That means, & should be noted that, if there had been an intended Status >difference in the Prog from which the GED originated it is lost in Legacy. >Q1. Can these GED labels be "drafted" to specific labels in Legacy, >especially ALIA which is likely to apply to a Surname rather than a GIVN or >NICK name? Your original post said something about the two alt. names being the same. From this post I am guessing that you mean the incoming GEDCOM contains a NICK tag and an ALIA tag that have the same values for a given individual. And I will further assume that the program that creates the GEDCOM is consistent and always creates both tags when a person has an alt. name. If so, then on the import into Legacy, why not use Customize to tell Legacy to ignore either NICK or ALIA? I haven't tried it since I don't have my hands on a GEDCOM that I can test with. -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools http://groups.yahoo.com/group/ltools 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://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
