I agree with you. That is why I show the smallest location I can be sure of, and in notes discuss what the smaller parts might be. And why I think that. Rich --- Dawn Crowley <[EMAIL PROTECTED]> wrote:
> Personally, I would read this: > , , , Germany > to mean that I know the person was from Germany, as > opposed to it is > highly probable that the person was in Germany for a > particular event. > > Also, some folks in the plains are just there--in > the plains. They are > in a county and possibly a township, but are not in > a city. Therefore, > I use: > near Hometown, Green County, Indiana > > I appreciate all of the insight that I get by > reading this group. It is > wonderful to see all of the sharing going on. Keep > it up! > 8^ ) > > Dawn > > > Krones2004 wrote: > > > I'm a little late jumping in on this subject but > this is what I do. > > > > Since Legacy likes us to put the location in the > location field in the > > order of: city, county, state, and country and to > use commas for > > missing compoents, I do this. > > > > If I know someone was from Germany but not where, > I would put in the > > location field the following: > > > > , , , Germany. > > > > Another example is a family I know was from > Bartholomew County, > > Indiana, but not the city, so I put the following > in the location field: > > > > , Bartholomew, Indiana, USA. > > > > This keeps my location database clean but also > lets me know I'm > > missing information. > > > > Peggy > > > > > > Tom Montgomery <[EMAIL PROTECTED]> wrote: > > > > It is my understanding that < > were used when > field size > > limitations were > > severe. With the capability we now have they > are not really > > necessary as we > > can pretty spell out exactly what we intend. > This is not to say > > that < > are > > no longer valid it is just they are not used > very often - don't > > see unless > > the recorded data has some age on it. > > > > TomM > > > > -----Original Message----- > > From: > [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > On Behalf Of > > Kathie > > Christensen > > Sent: Monday, February 26, 2007 8:54 AM > > To: LegacyUserGroup@legacyfamilytree.com > > Subject: RE: [LegacyUG] "Probably" as part of > the locacation (WAS > > as part of > > the date) > > > > I thought < > were used around approximate or > probable dates and > > places. In > > the export file window of Legacy this option > is listed: > > "Suppress and " > > > > Kathie > > > > > -----Original Message----- > > > From: > [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] > On Behalf Of > > Glen > > > Ballard > > > Sent: Monday, February 26, 2007 8:24 AM > > > To: LegacyUserGroup@legacyfamilytree.com > > > Subject: RE: [LegacyUG] "Probably" as part > of the locacation > > (WAS as > > > part of the date) > > > > > > > > > Ralf, > > > > > > According to couple of books I have on > genealogy, the word "OF" > > is the > > > genealogical equiv. of Probably. I use the > following format: > > > > > > Of Orem, Utah Co., Utah, USA > > > Of, Utah Co., Utah, USA > > > Etc... > > > > > > Glen Ballard > > > > > > -----Original Message----- > > > From: > [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] > On Behalf Of > > > ralf_x > > > Sent: Monday, February 26, 2007 5:08 AM > > > To: LegacyUserGroup@legacyfamilytree.com > > > Subject: Re: [LegacyUG] "Probably" as part > of the locacation > > (WAS as > > > part of the date) > > > > > > From searching the archives, I am not > totally clear. > > > > > > Is it preferred to leave a location blank or > put in a probable > > > location "Probably Vancouver, British > Columbia, Canada"? > > > > > > Is there a standard for this? Is there a > location (book, > > webpage, etc) > > > where standards such as this are listed? > > > > > > Thx! > > > > > > Ralf > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam > protection around > > > http://mail.yahoo.com > > > > > > > > > Have you unlocked the real power of Legacy? > Legacy 6.0 Deluxe > > has 92 > > > features not found in the Standard Edition. > Learn more about these > > > features at > http://legacyfamilytree.com/DeluxeEdition.asp. > > > > > > Legacy User Group 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@legacyfamilytree.com/ > > > > > > For online technical support, please visit > > > http://www.LegacyFamilyTree.com/Help.asp > > > > > > To unsubscribe please visit: > > > > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > > > > > > > > > > > Have you unlocked the real power of Legacy? > Legacy 6.0 Deluxe > > has 92 > > > features not found in the Standard Edition. > Learn more about these > > > features at > http://legacyfamilytree.com/DeluxeEdition.asp. > === message truncated === Have you unlocked the real power of Legacy? Legacy 6.0 Deluxe has 92 features not found in the Standard Edition. Learn more about these features at http://legacyfamilytree.com/DeluxeEdition.asp. Legacy User Group 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@legacyfamilytree.com/ For online technical support, please visit http://www.LegacyFamilyTree.com/Help.asp To unsubscribe please visit: http://www.LegacyFamilyTree.com/LegacyLists.asp
