On Tue, 07 Feb 2012 07:14:16 -0800 Paula Ryburn wrote: > Tony, did you submit the Location AKA suggestion? or something > different? > --Paula in Texas
My suggestion was called "Date-linked location names". The basic idea was to have a "Location" master file (or table) with all the tags, Latitude and longitude data etc. and a chain of Long-name/short-name pairs which have a "to" date and their own preposition. If this is implemented we can have a single location, but have the short and long names varying by date, so Location: The generic name for the location to 1837: The, oldest, long, name: a short name for this to 31 mar 1957: A, Different, Long, Name: Another short name to: The, current, long, name: the current short name. To 1837 implies up to and including 31 Dec 1837. A blank date implies to the current date. The Location record would have a location name which may, or may not, be in CSV format. I also suggested that there be a new [Location] for sentence definitions. Obviously, the program would pick the appropriate long or short name depending on the date, defaulting to the location name if either there was no date in the event or if the date was out of range (if I omitted the last line above and the date was after 31 Mar 1957) Seems to meet all criteria, I think? Tony 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 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
