[snip] If Legacy (or any other gen program) adopted the scheme I have suggested for identifying places by assigning a "type" tag with each place, then the the program doesn't have to "get too smart in trying to decipher which bits of the text string are which!" Each "bit" will be defined as a City, State, County, Province or whatever. In order to write out a report, we only need to assign each type to a level. So for example, when the program sees an address it knows that's Level 1 and that when it sees a City that's Level 2 etc. One could have multiple government entities at the same level, so State and Province could both be Level 3 so that US States and Canadian Provinces would print just before the country.
jr
I would like to add a vote for John's proposed method of handling locations.
I don't see another good way to resolve the location dilemma.
In addition, those who are working on a possible future GEDCOM version are using this approach.
Dean L. Bennett
Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
