What does AQ do when you export a sample with an alternate name to ged 5.5? Where is it put? If as a secondary name ala Legacy, then it looks like AQ just isn't built to import correctly.
Wm Voss -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jim Winfrey Sent: Saturday, 19 June, 2004 17:29 To: [EMAIL PROTECTED] Subject: RE: [LegacyUG] Name Prefix and Suffix/Middle name field Wm, I have a registered copy of AQ11 and could not get it to import AKAs as such. There is a tick mark beside the given name field that shows all name variants, including nicknames, that are imported but I couldn't find a separate field for AKAs. I'm wondering if we are understanding Ron's issue. A number of tests with different software programs worked OK and the one he used to show how it might ought to be didn't work. This is a mystery. Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wm Voss Sent: Saturday, June 19, 2004 7:54 PM To: [EMAIL PROTECTED] Subject: RE: [LegacyUG] Name Prefix and Suffix/Middle name field I just downloaded and installed Ancestral Quest and attempted to do just as you did: ERROR 1: bob2.GED, line 22: Cannot specify more than one name per individual. 1 NAME Bob // 2 GIVN Bob 2 SURN I tried to add an alternate name and export a ged from the program, but that feature is disabled in the demo and I have no desire to buy it. Perhaps Ron can do a similar test and post up the gedcom text that AQ produces for an alternate name? Time to uninstall now. Wm Voss -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jim Winfrey Sent: Saturday, 19 June, 2004 16:39 To: [EMAIL PROTECTED] Subject: RE: [LegacyUG] Name Prefix and Suffix/Middle name field Ron, I just tested your AKA claims by creating a one person database in Legacy and assigning the person several AKAs. I exported the database to a gedcom and imported it into Rootsmagic, Genbox, and FTW. The AKAs transferred correctly in all cases. Then I created a gedcom from each of these and imported these gedcoms into Legacy - again it worked correctly. Last test was to import the Legacy gedcom back into Legacy and, of course, this worked correctly also. What did I do/or not do that would create different results than you got? Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ron Klotz-Zellhoefer Sent: Saturday, June 19, 2004 6:57 PM To: [EMAIL PROTECTED] Subject: Re: [LegacyUG] Name Prefix and Suffix/Middle name field Well, Ron, never heard of GenBox, but I'm not here to tout AQ, but it at least has a totally sortable Index View which I (and Legacy) need very badly rather than screwing around with the back/forth between GenViewer and Legacy. But the AKA>GEDCOM problem appears all the time. I've seen AKA's transfer at all, I've seen only one AKA transfer and then show up in the receiving file as the main name rather than an AKA, and even a recent "Direct Import" of a Legacy file to TMG v.5 didn't get the AKA's. I have NEVER seen AKA's transfer fully and/or correctly, including to phpGedView reading a GEDCOM 5.5 directly. If you take some time to look at the fields available in a Legacy Export file, no matter which format is used (even Legacy's own) there are no fields for AKA or _AKA, nor for Location coordinates, and I don't yet know for what else, but I am sure there are more. Legacy fields which ARE available for GEDCOM export do include _Tag1 ... _Tag9, which are not data and normally disposable without impact. I can live without the new Location Finder, but am having a very hard time dealing with missing for dysfunctional basic tools. RonKZ ----- Original Message ----- From: "Ron Bernier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, 19 June 2004 14:05 Subject: Re: [LegacyUG] Name Prefix and Suffix/Middle name field Ron, I beleive the problem lies with AQ, not Legacy. I created a GEDCOM from Legacy and imported it into GENBOX. All of my AKAs carried to GENBOX as "Other Name". I did not loose a single AKA. Ron Klotz-Zellhoefer <[EMAIL PROTECTED]> wrote: from Dennis: >This may have been discussed earlier (I don't feel like going on a scavenger >hunt to find it), but why can't AKA be used in this instance? using V.5 latest.... I am at this moment dealing with yet another horrible experience with Legacy's AKA's (and more). I have loved that AKA button, and AKA's seem also be a great place to store those farmname/surnames, but... .... NEVER unless Legacy fixes it's GEDCOM output to include (ALL) it's proprietary data-fields. I just exported a new GEDCOM and imported it with Ancestral Quest (because of it's completely sortable index view, on which I am being completely ignored by Legacy). I spent considerable time during the export setup looking over the various formats and examining the export data-items. NOW HEAR THIS! Regardless of export format used, Legacy's AKA's are NOT in that list. They are also not written to GEDCOM's "Alias field". NEITHER are Location Coordinates, on which I have spent so many many hours. Also apparently missing are all or most of Legacy's unique data-items - that I will be checking further AND upon importing to AQ, of course nothing of all those efforts is anywhere to be found. I have grown hugely disgusted with all this, and am coming to feel it is completely deliberate, because one can't use any other gen-app to deal with Legacy's shortcomings. The only alternative seems to be to switch, and do tons of rework, and never even attempt to return to Legacy, because one would have to rework it all over again. I am not a GEDCOM fan at all - it's tons of problems in it's own right. But, GEDCOM is the only import/export tool we really have, and even tho' it's "bad", it does appear that it can handle additional data-fields if told to so so. For me, it's 8 years of full-time work on the line ... and to think I began this day in a great mood! RonKZ Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp ===== Ron Bernier Woonsocket, RI Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
