On Thu, 18 Nov 2010 19:53:47 -0000, "Ron Ferguson" <[email protected]> wrote:
>That is >that there is *no* compromise, one cannot compromise with facts, and the >fact is that we do not construct our locations in a set format. Broadly >speaking we go from the smallest place to the highest, but the number of >steps in between can vary wildly. Ron: The original poster specifically asked about "Lincoln, Lincolnshire, England". You are (of course) correct to say that it should be displayed this way on reports and web pages (and exported). But for the purposes of sorting the Location List, what would be the harm in entering an extra comma? i.e. "Lincoln, Lincolnshire, , England". One normally assumes that the blank placeholder means that a piece of information is "missing" or "unknown". But a user could also use this to mean "does not apply". It would just be a way to trick Legacy into sorting the list in a desired order. No more, no less. Since extra commas can be removed in the output, does this really matter? My discussion with Jerry was essentially a quarrel over "what is the best way" to do something. My stance is that the "best way" depends on what you wish to accomplish. If standardizing on 4 fields provides a benefit, go for it. If one can get the job done with an indeterminate number of fields, go for it. That being said, if I were a stickler for a 4 field convention (which I am not), I would go ahead and use that as the long location name. But I would enter the 3 field (correct) location name as the short location name and display that on all reports and web pages. I don't think there is an option to export the short name in place of the long name (or to remove extra commas). Maybe there should be. *** My comments can be extrapolated to include 5 (or more) field conventions if desired. Maybe "city, township, county, state/province, country". Or "street address, city, township, county, state/province, country". If a field does not apply, just leave a placeholder. *** Just discussing ... not recommending any particular method. -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools http://groups.yahoo.com/group/ltools 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
