The previous genealogy program I used had you put "Co." after the county name so you had place location of Little Rock, Pulaski Co., Arkansas, USA
However in the Legacy training and the Geo Database it does not use or seam to like the "Co." on the end. Thus output was: Little Rock, Pulaski, Arkansas, USA When I moved to Legacy I pulled "Co." off of everything as I found it trying to follow the convention. Now in some of my reports and other things I look back and think it might have been nice to have had the Co. for the County. So my questions are: What is the reasoning Legacy does not put them on? Are there reasons not to have the Co. on the end? I did note in some reading that if you just have the county name then your are supposed to put "Co." or something on the end so people don't get confused and think it was a City. So why not allow it all the time. Anyone else just force it on? It means you can't use the default lookup in the Geo Database. It certainly would be something easy to fix and add as a feature to Legacy to have it put Co. on county names on if it did not cause problems. Is there a research/genealogical reason not to do this? Anyone else ever run into this question? thoughts? thanks Alan 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://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
