I am sorry but we seem to be missing the main point. This problem was created 
by FTM
originally, when it allowed occupations to be in the same field as locations. 
When 
recieving a gedcom, you can not tell if the ORIGINATING file was from  FTM.
I never used it, because when I saw the display of FTM at a convention, I RAN 
AWAY.
Legacy has found ways to fix problems created by FTM, but it isn't pain free. 
" You could end up with people named Massachusetts Boston!"   More likely you 
cousin 
will be living in Blacksmith 1718-1750.
L does find ALL places that do not make sense to the DB, and asks you do you 
want to
fix it? 
If you may forget what you will call the various fields (Country, County, 
Parish). Change
then in the SORT CHOICE. Otherwise, consistancy is unobtainable.
" In the Location1Name field a user could put "Address".
> > In the Location1Data field a user could put "25 Main Street""
Don't worry about how anyone else does it, make sense to yourself. 
Anyone who wishes to get a little better clarity may write to me OFF List, but  
the people 
who need help are being frightened away.
I will help
Rich in LA CA on the LUG list on main web page.

-----Original Message-----
From: Gene & Rusty <[EMAIL PROTECTED]>
Sent: Dec 14, 2004 12:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [LegacyUG] Back to Basics

Just 2 cents here,

   but I've never had a problem importing/exporting
    ged.coms back and forth and never had a field
    or location problem.

   Hope this helps,

      gene

----- Original Message ----- 
From: "Jane Hakes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 14, 2004 2:26 PM
Subject: RE: [LegacyUG] Back to Basics


> Yes, but what happens when you try to import/export GEDCOM files that
> don't use these same field designations?! If Legacy provided some way to
> map these fields to standard GEDCOM field descriptions when
> importing/exporting them, then it would work. Otherwise it would be a
> nightmare. You could end up with people named Massachusetts Boston!
> 
> Jane Hakes
>  
> 
> > -----Original Message-----
>  
> > What follows is a bit long and perhaps a bit technical.
> > 
> > Legacy would have a group of Location Fields for each Location.
> > They would have the name Location1, Location2... LocationN.
> > Each of these fields would have two subfields, a Name and the Data.
> > So in Access Database terms there'd be a table or table 
> > fragment with Location1Name and Location1Data fields etc.
> > In the Location1Name field a user could put "Address".
> > In the Location1Data field a user could put "25 Main Street"
> > 
> > Another user could do things differently and In the 
> > Location1Name field put "City"
> > In the Location2Data field put "Albany"
> > Note this varies for EACH EVENT.  So the user could use the 
> > above scheme for one event and the following for another 
> > event Location1Name field = "Village"
> > Location2Data field = "Lake George".
> > So this is completely flexible and instantly international, 
> > because even the types of the jurisdictions change and they 
> > can do so from any event to any other event.  One could then 
> > search for all "Villages" describing a certain location level.
> > 
> > So you could find and mark all events or people who had 
> > events with "County" in a certain place location type.  Then 
> > Search among the marked records only for place location name 
> > of "Cork".  These two searches would yield all the folks who 
> > had County Cork as a location.
> 
> 
> 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


Rich in LA
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

Reply via email to