Hello again Arthur,
No need to answer the questions. I was able to recreate your scenario. In my test scenario.............. In the Alexandra Nursing Home record, it put the value in the Legacy 'Address Name' field at the very top of the address screen. The 'Address' field (which appears to be designed for a street address) is blank. In the 41 Carey Street example, it recognized it as a street address and put it in the 'Address' field. Every record needs an 'Address Name', so it stuck in n/a. This kind of issue (I hesitate to call it a problem, it's certainly not a bug) is simply the result of different database designs between two different programs. Roots Magic crams the 'address' in one field, Legacy has separate fields for the 'Name' and the 'Street' should you choose to use them. One could imagine a scenario where the Alexandra Nursing Home is at 41 Carey Street. In Roots Magic, you would put "Alexandra Nursing Home, 41 Carey Street" in Place Details, in Legacy you would put "Alexandra Nursing Home" in Address Name, and 41 Carey Street in 'Address'. Neither is right or wrong, they are just different. It looks to me like the Legacy Gedcom import tries to interpret the single ADDR tag as either a 'name' or a true 'street address' and put the value in what it considers the most appropriate field within it's data structure. Paul Gray -----Original Message----- From: Paul Gray [mailto:[email protected]] Sent: January-18-15 12:06 AM To: [email protected] Subject: RE: [LegacyUG] Event Addresses - PLUS A MUCH MORE SERIOUS ISSUE Hello Arthur, I have Roots Magic in addition to Legacy, and I am trying to recreate the issue. But I need to verify a few things. In your examples, where exactly in Roots Magic were you storing the two values 'Alexandra Nursing Home' and '41 Carey Street'? Was it in 'Place Details' immediately under 'Place' on the edit event screen? Once imported in Legacy, where are you seeing those values? Is it in the address screen? Which fields have which value? I assume they are in (or spread across) Name, Sort String, and Line 1 of address. Particularly interested in n/a 41 Carey Street is the n/a and Carey street in one field or two? Paul Gray -----Original Message----- From: Arthur & Pauline Kennedy [mailto:[email protected]] Sent: January-17-15 11:11 AM To: [email protected] Subject: Re: [LegacyUG] Event Addresses - PLUS A MUCH MORE SERIOUS ISSUE If what you say is correct, then perhaps I should have been asking why some of the addresses *don't* have "n/a" prefixed, rather than why some of them *do*. You'll see from the GEDCOM extracts that I provided before that both addresses have a PLAC tag followed by a single ADDR tag with no further details. One ended up with the "n/a" and one didn't. However, this file that I imported doesn't in fact contain any _NAME tags at all, so presumably the discrepancy is down to something that Legacy has done. (Looking at the whole of my file, Legacy reports that I have 150 event addresses, and on a quick count, it appears that 39 have had "n/a" added, leaving 111 that haven't.) Looking into this further, I decided to export a GEDCOM file from Legacy and compare it with the one I had imported, and I found that in some places the events and their addresses had indeed been changed. Using the events I quoted before, I found: original version: 1 DEAT 2 DATE 22 FEB 1952 2 PLAC Harrogate, WRY 2 ADDR Alexandra Nursing Home 2 SOUR @S171@ 3 _TMPLT 4 FIELD 5 NAME Page changed to: 1 DEAT 2 DATE 22 Feb 1952 2 PLAC Harrogate, WRY 2 SOUR @S79@ 2 ADDR Alexandra Nursing Home 3 _NAME Alexandra Nursing Home This one looks OK in Legacy, but see my point 2 below on use of the _NAME tag. (And I presume the sources have been re-numbered.) Now the second one: original version: 1 CENS 2 DATE 6 APR 1891 2 PLAC Middlesbrough, NRY 2 ADDR 41 Carey Street 2 NOTE Age 7, born Middlesbrough; Scholar. 2 SOUR @S12@ 3 PAGE RG12/4014 fo27 p5 3 _TMPLT 4 FIELD 5 NAME Page 5 VALUE RG12/4014 fo27 p5 changed to: 1 CENS 2 DATE 6 Apr 1891 2 PLAC Middlesbrough, NRY 2 ADDR n/a 3 CONT 41 Carey Street 3 _NAME n/a 3 ADR1 41 Carey Street This raises a number of questions/issues: 1. I still don't understand why one address was changed and not the other. 2. On my reading of the GEDCOM standards_NAME tag is a non-strict part of the ADDR definition; it therefore concerns me a little that Legacy should be using it in an exported .ged file, and I'd be even more concerned if it were suggested that its use was required in any .ged file that was imported into Legacy. However, manually editing 39 addresses pales into insignificance compared to what I have now discovered: 3. With the second event quoted here, as well as the address being changed, the Event Notes and Source have totally disappeared. They are simply not there, either in the main Legacy database or the GEDCOM it exported. I use Event Notes extensively, and of course Sources, and this loss is catastrophic. As far as I am concerned, this is a deal-breaker. I have already spent a long time trying to understand and deal with issues that I have come across, and sorting this one out is more than I can contemplate. In case this is something that can be sorted promptly I shan't do anything hasty, and will wait for a response before uninstalling Legacy. Thank you to those who have tried to help me, Arthur On 17/01/2015 02:48, Sherry/Support wrote: > 1 ADDR Lillie Alice Taylor > 2 CONT 124 S. Main > 2 CONT Dillon, MT 59725 USA > 2 _NAME Lillie Alice Taylor > 2 _SORT Lillie Alice Taylor > 2 ADR1 124 S. Main > 2 CITY Dillon, > 2 STAE MT > 2 POST 59725 > 2 CTRY USA > > Ensures that there is a name for the individual's address. > > For a Source Repository: > > 0 @R37@ REPO > 1 NAME Eastern Arizona Courier > 1 ADDR Eastern Arizona Courier > 2 CONT 301 E. Hwy 70 > 2 CONT PO Box N > 2 CONT Safford, AZ 85548-2010 > 2 _NAME Eastern Arizona Courier > 2 _SORT Eastern Arizona Courier > 2 ADR1 301 E. Hwy 70 > 2 ADR2 PO Box N > 2 CITY Safford > 2 STAE AZ > 2 POST 85548-2010 > 1 PHON (520) 428-2560 > 1 [email protected] > 1 _URLhttp://www.eacourier.com/ > > And for an Event address > > 2 ADDR Minneapolis City Cemetery > 3 CONT 123 Main Street > 3 CONT Minneapolis, Minnesota > 3 _NAME Minneapolis Cemetery > 3 ADR1 123 Main Street > 3 CITY Minneapolis > 3 STAE Minnesota > > > Note that all three have a name assigned to the cemetery. With a name, > then it would show as n/a > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Fri, Jan 16, 2015 at 11:05 AM, Arthur & Pauline Kennedy > <[email protected]> wrote: >> Hi Sherry >> >> Thanks for the reply. The GEDCOM was created in RootsMagic (v.6). >> Like Legacy, it allows for an Address field as well as the more >> general Location. I don't know anything about the underlying database >> structure in RootsMagic, but in the user interface, addresses are >> linked to the locations they refer to. So first of all you select the >> location (generally a town or parish etc) and then you have the >> opportunity to select or add a specific address (street, church, cemetery >> etc). >> >> However, your suggestion about an Address name seems not to apply in >> my case. This is what I wrote earlier: >> >>> This event imported with the address intact: >>> 1 DEAT >>> 2 DATE 22 FEB 1952 >>> 2 PLAC Harrogate, WRY >>> 2 ADDR Alexandra Nursing Home >>> 2 SOUR @S171@ >>> 3 _TMPLT >>> 4 FIELD >>> 5 NAME Page >>> >>> but with this one the address went into the list as "n/a - 41 Carey Street": >>> 1 CENS >>> 2 DATE 6 APR 1891 >>> 2 PLAC Middlesbrough, NRY >>> 2 ADDR 41 Carey Street >>> 2 NOTE Age 7, born Middlesbrough; Scholar. >>> 2 SOUR @S12@ >>> 3 PAGE RG12/4014 fo27 p5 >>> 3 _TMPLT >>> 4 FIELD >>> 5 NAME Page >>> 5 VALUE RG12/4014 fo27 p5 >> Do you have any other suggestions, please? >> >> Arthur >> >> 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 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5645 / Virus Database: 4260/8946 - Release Date: 01/17/15 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 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5645 / Virus Database: 4260/8949 - Release Date: 01/17/15 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
