Have you checked the GEDCOM, you can open it in any text editor. You can then see if the change is on export from whatever program, or on import into Legacy.
Ron Ferguson http://www.fergys.co.uk/ Arthur & Pauline Kennedy <ken...@paxnet.co.uk> wrote: >I've have some help on this, but nothing really got to the bottom of how >or why "n/a" gets inserted into some of the event addresses when I do a >GEDCOM import, and whether there is anything I can do about it, before, >during or after the import. > >As I said in a different message, it makes we wonder (and worry) whether >there were any other unwanted changes to my data when I imported it. > >Can anyone help further, please? > >Arthur > > >On 12/01/2015 19:30, Arthur & Pauline Kennedy wrote: >> No replies to my query below yet, so here's a bit more information in >> case that inspires a response. >> >> In relation to point 2, I've inspected the .ged file that I imported, >> and just don't understand why this happened. >> >> 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 >> >> Any thoughts welcome - and also on points 1 and 3 of my original query. >> >> Arthur >> >> >> On 10/01/2015 20:27, Arthur & Pauline Kennedy wrote: >>> I'm thinking of returning to Legacy after an 8-9 year absence and have >>> been looking at the Standard version (8.0.0.459). I'm trying to work out >>> how I would deal with Event Addresses, which appear to be handled a bit >>> differently from the program I am currently using. >>> >>> <snip> >>> >>> 2. Some of the imported addresses show "n/a - " before the address. What >>> does this mean, and is there a way to prevent it? >>> >>> <snip> > > > > > > >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
