Hi Jane, This is a procedure that I use to add ‘USA’ to the end of locations…
BACKUP your file first. Read the CAUTION note below… Go to Search/Search and Replace (Ctrl H) Select Lists-Location Check ‘Ends With’ (Important) Check ‘Replace only found text with replacement text’ (Important) Find What? ‘, Indiana’ (note: I’ve used comma/space/Indiana) Replacement text ‘, Indiana, USA’ (again comma/space/Indiana, USA) This will replace all locations ending in ‘, Indiana’ with ‘, Indiana, USA’ 16 College Avenue, Bloomington, Monroe County, Indiana will become 16 College Avenue, Bloomington, Monroe County, Indiana, USA It will not change 16 College Avenue, Bloomington, Monroe County,Indiana (no space between the comma and Indiana) If you are less cautious you can skip the comma/space. * * CAUTION… * * Be sure to have a backup of your file. Check your file after to be sure you haven’t made major unplanned changes. When you click on ‘Start’ it will take you to the first instance it finds and you have the choice to ‘Replace’ or ‘Replace All’. ‘Replace’ will step you through one change at a time. ‘Replace All’ does just that. There is no ‘Undo’ This will change any location ending in ‘, Indiana’ to ‘, Indiana, USA’ It is possible that another location ends in ‘Indiana’ that is not in the USA – this will be changed as well. I use the comma and space to further limit what it finds. Be sure to include the comma and space before the place name in both the ‘Find What’ and ‘Replacement Text’ You may wish to repeat this (or similar) procedure for ‘List-Location-Short’ You will have to repeat this procedure for every state in the USA. The reason for selecting ‘Ends With’ is to prevent replacing the word ‘Indiana’ elsewhere in the field and to skip those that already end in ‘USA’ (or something else) You don’t want Indiana, USA, USA. * * If you are faint of heart - use the same procedure as above but use ', Indiana' as the text for 'Find What' AND 'Replacement Text'. Then manually edit the text in the 'Replacement' box and do each one individually. By using the same wording for both steps it will simply replace the found text with the exact same text if it is not one you wish to change, or if you accidentally hit the wrong button. Copy and paste ', USA' will work here. I think this is what you were trying to achieve. Bob From: cranberryf...@cobridge.tv [mailto:cranberryf...@cobridge.tv] Sent: Thursday, November 10, 2011 1:25 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Master Location list revision No! It won’t delete anything in that field, it will only add the , USA to the end. The location field is set up to have 4 place holders but you can have more than that if you want. 16 College Avenue, Bloomington, Monroe County, Indiana will become 16 College Avenue, Bloomington, Monroe County, Indiana, USA michele From: sarlesinsi...@gmail.com Sent: Thursday, November 10, 2011 4:18 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: Re: [LegacyUG] Master Location list revision So, if I have 16 College Avenue, Bloomington, Monroe County, Indiana and I convert it to Bloomington, Monroe County, Indiana, USA I will lose the address, right? Jane On , cranberryf...@cobridge.tv wrote: > > > > > It will effect anything in a location field. > > > > Purvis, Lamar, Mississippi > > will become Purvis, Lamar, Mississippi, USA > > > > If you have a cemetery name in a location field then this will > happen... > > Grantham Family Cemetery, Lamar, Mississippi > > Grantham Family Cemetery, Lamar, Mississippi, USA > > (cemetery names really don’t go in a location field but many people do > it). > > > > michele > > > > > > > From: sarlesinsi...@gmail.com > > Sent: Thursday, November 10, 2011 3:47 PM > > To: LegacyUserGroup@LegacyUsers.com > > > Subject: Re: Re: [LegacyUG] Master Location list > revision > > > > > > > And > when I do that, what happens to the detail I put in the @1 position (town or > cemetery name, etc.) > > Jane > > On , cranberryf...@cobridge.tv > wrote: > > > > > > > > > > Yes! You CAN do it > globally! Go to the MASTER LOCATION List > > screen. At > the top right click OPTIONS. Then click > > EXPAND/CONTRACT > LOCATION PARTS. Then on the right side check the box that > > says > ADD USA (or add United States, whichever your prefer) and you are done > > > > > > > > > michele > > > > > > > > > > > > > > > From: sarlesinsi...@gmail.com > > > > > Sent: Thursday, November 10, 2011 2:26 PM > > > > To: > LegacyUserGroup@LegacyUsers.com > > > > > > Subject: [LegacyUG] > Master Location list revision > > > > > > > > > > > > > > > I > > did a bad job on my locations early on. I have > almost no genealogy data out of > > the country, so I ignored the "USA" > part of the location and put the State > > there. Now, I see that it was a > mistake and would like to change to the format > > as outlined on the > training video. > > > > My question is: Is there a way to do > > > this at all globally, or must I attack each entry in my whole location master > > > list one at a time? That will take many days (even weeks) to > accomplish, I'm > > afraid. Suggestions appreciated. > > > > Jane > Sarles > > > > 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 > > > > > > > > > No virus found in this > > message. > > > Checked by AVG - www.avg.com > > Version: 10.0.1411 / Virus > > > Database: 2092/4007 - Release Date: 11/09/11 > > > > > > > > > > > > > > > > > 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 > > > > > > 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 > > > > No virus found in this > message. > Checked by AVG - www.avg.com > Version: 10.0.1411 / Virus > Database: 2092/4007 - Release Date: 11/09/11 > > > > > > > > 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 > > 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 ________________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1411 / Virus Database: 2092/4007 - Release Date: 11/09/11 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 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
