Well said and I hope this puts it to bed Brendan Caley
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leon Chapman Sent: Friday, April 22, 2005 5:54 PM To: [email protected] Subject: RE: [LegacyUG] about Locations Folks: Today in Legacy, the Location field is 255 characters in Length. In my testing, I can divide that field into as many fields as I want as long as I don't run out of the 255 characters including a comma and space after a field. That all translates to about 15 fields where each field has 17 characters (included a comma & space afterward). If there is a limit that Legacy has, it is that Legacy only Sorts on the 1st 9 fields of a location. I personally do not ever see me or anyone using 9 fields for a location. The user can DEFINE and SORT for their use any definition they please for these 9 or more fields (Note: The 1st four fields are predefined for reference purposes as: City, County, State/Providence, Country, but you can always use your favorite AKA for these to redefine them if you like -- you just have to remember the AKA and enter your data appropriately). I use the "City" field for cities, cemeteries and churches. If I wanted to, I could add two fields to my locations (by using commas) to support a cemetery field and a church field, then I could sort on cemetery or churches. Legacy users currently have the option to define for their specific database any order and how many fields until the 255 character limit is reached or the 9 sort fields becomes a limit. So, I ask, what more flexibility does the user need? If the 255 characters is a limit or the 9 sort fields are a limit, I am sure the developers could quickly address those issues. For all of my locations in the USA or World Wide, I have the maximum flexibility to utilize fields any way I wish. I believe this discussion all comes down to the users not wanting to enter an extra comma in their location fields to define and use a new field. ------> I for one, do not want the location field structure changed because I have the maximum flexibility it use the current structure any way I choose. <------ Leon Chapman [EMAIL PROTECTED] --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0516-7, 22/04/2005 Tested on: 22/04/2005 18:07:22 avast! - copyright (c) 1988-2004 ALWIL Software. http://www.avast.com 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
