Hi Jack,
I enter locations as you do. I also add street addresses, cemeteries etc as I prefer the way it shows on reports. I see no need to lock myself into a US 4 field location - especially if it introduces commas for non-existent fields. Even Gedcoms don't have a problem with more or less location fields. I haven't used the Geo Database.
There is no problem in finding all the locations in and around say Sherborne, Dorset.
Just sort the location list from right to left.
Provided you have always concluded the location County, Country, they'll all be together.
To get a list of all the people, just highlight all locations including Sherborne and Show List.
You can't do fancy sorts this way as Legacy has locked country into 4th field instead of into 9th and you can't change it.
I would like to be able to sort from right to left and then have country as 1, county/state 2, town 3 etc. Then you could bring the town to the front.
Cheers, Cathy
At 05:22 PM 3/12/2004, you wrote:
Ron,
To define location as you do presupposes that genealogy is totally based in USA. I don't believe that many people in the UK (or other countries) would wish to insert that extra comma between town/city and county. It looks meaningless on any report produced. OK that is how the Geo database holds it, but that doesn't make it correct, just reinforces that the database is US centric.
Maybe I am breaking hallowed rules, but for UK locations I use village, town, county, country or town, county, country. Of course that means I can't easily find all locations in villages around a larger town and would welcome suggestions for improving the ability to search - but I hate adding meaningless commas!
Jack
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
