Anne, With respect, I am a Lancastrian and my family is of Cumberland descent, and if it wasn’t for the fact that I have some experience of genealogy I would have some difficulty in recognising those locations.
I too set the Location List to read from right to left, but I put the Street as a separate field. That aside, Liverpool, Lancashire, England is the location, there is no field between Liverpool and Lancashire. As you can see, I also have no problem in going directly to Liverpool Lancashire. The problem I see is when you have district, of Liverpool eg. Everton, Liverpool, Lancashire, England, or Wavertree, Liverpool, Lancashire, England, which one should also have for Liverpool, btw. I’m afraid that I simply find your system for our locations confusing, and our lack of a system is confusing enough, but then “Whatever works for you...”. Ron Ferguson http://www.fergys.co.uk/ From: Anne Hollingshead Sent: Saturday, August 27, 2011 2:06 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Getting rid of commas Ron, The benefits I find are ease of use. If I have many entries for the same town/city ( I am not hung up on what a town is or how big it is I just use common usage) I put Liverpool, , Lancashire, England Liverpool-9 King St, , Lancashire, England Liverpool-St Peter's Church, , Lancashire, England This way when I enter a new Liverpool location I immediately go to Liverpool, , Lancashire, England from there I click on the arrow and can check if I already have an entry for an address for that town. If not I quickly create a new one selecting and editing e.g. Liverpool, , Lancashire, England When I go to the location list I have all my entries for each town together. I have quite a few farm names or farm settlements so Longtown-Oakbank, , Cumberland, England I use the third position for counties or states whichever is relevant to that country. When I sort I can immediately see e.g. all my Cumberland entries. I use the second position for suburbs in large cities. Camberwell, Melbourne, Victoria, Australia It works for me. Anne On 27/08/2011 6:07 PM, Ron Ferguson wrote: Anne, I would be interested to learn what you consider to be the benefits of the 4 field convention. Frankly I cannot really see anything worthwhile for non-Americans. Ron Ferguson http://www.fergys.co.uk/ From: Anne Hollingshead Sent: Saturday, August 27, 2011 4:03 AM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Getting rid of commas Then the only way to overcome the problem would be to use an rtf file and search and replace ", ,". ? Is that right ? This can only be done in a few reports though ? Can Legacy find a way to solve this problem so that non US users can benefit from the 4 place system ? Anne On 27/08/2011 1:58 AM, Brian/Support wrote: Jenny, You are correct, the format option in the reports are only for leading commas not those embedded within the location. Brian Customer Support Millennia Corporation mailto:br...@legacyfamilytree..com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. On 26/08/2011 6:16 AM, Jenny M Benson wrote: I may be wrong about this, but to me "leading commas" means commas at the START of a location, such as ",,New Jersey, USA" or ", Passaic, New Jersey, USA" so I would not expect either of the options above to remove commas which indicate that a later element is missing, such as "Clifton,, New Jersey, USA." 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://www.LegacyFamilyTree.com/Help.asp 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
