I'll let Cathy speak for herself, but I see the problem with fixed boxes is that it creates a "one size fits all" solution. In some places we want a box to mean County in others State, unless you create individual boxes for each conceivable type of location field. Then how do you string them together in reports? This is location specific.
Not sure what the ideal solution is, but I don't like the idea of fixed fields!
Rob
----- Original Message ----- From: "John R. Bayle" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 12, 2004 11:20 AM
Subject: Re: [LegacyUG] Back to Basics
In replying to my posting, Cathy wrote:
<big snip>
Certainly, we don't want to go backwards and have separate fields/boxesforeach part of a location.
Boy, Cathy you and I sure have different views of this issue! I think a separate field for each location part is a good thing, just like it's a good thing for names.
Seems to me that it solves your sorting problems. You just say Sort by counties, and all the Washington counties go together, whether they were in the same state or not. Or you could sort first on counties and then on states. Then all the Washington counties in New York would be together and all the Washington counties in Ohio wold be togther but the NY and OH counties would be separate from each other, etc.
Tell me what I'm missing here! jr
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
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
