LUGers
I have used ABT (about) for estimated dates and
have found Legacy understands and can calculate
ABT dates. When I type 'about', Legacy changes
it to 'abt'. Also when I submit my GEDCOM file
to my Danish comparison service, GEDCOMP (see
http://www.lklundin.dk/gedcomp/english.php )
it understands the 'abt' date and can compare
it to dates in other GEDCOM files.
I suggest using 'about' or 'abt' for estimated dates.
Also I suggest entering an estimated date over not
entering a date, when the date is unknown.
Jim
[EMAIL PROTECTED]
Ron Klotz Zellhoefer wrote:
> Sandra,
>
> Legacy appears to "understand" date prefixes such as Est, Abt and Cir,
> which are not reported by Legacy as "Bad Dates"; a reason to avoid "me
> 1887" or "SD 1887 SD", etc.
>
> I'm not sure about which such formats are usuable in calculations, but
> certainly non-standard date formats won't work.
>
> I feel that most anyone would understand "Est" as just some sort of
> educated guess, so see no need to further identify or source such, as it
> can be replaced with a verifiable date whenever found.
>
> I remember years back having pehaps 25 people in my list who were named
> "Maria", not other data -- no surname, no dates, nadda! Using an Est
> date really does help!
>
> HTL
> RonKZ
>
> Anyway,
> ----- Original Message ----- From: "Sandra Duncan"
<[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, 27 May, 2005 08:54
> Subject: Re: [LegacyUG] learning from mistakes
>
>
>> Hi Ron
>> I do not always enter a birth date but because of you I MAY start. I
>> have discovered that when I calculate a date from provided data such
>> as died
>> 8 may 1748 age 79 y 3m 2d I can enter b. cal [calculated] 6 Feb 1668 and
>> nothing bad happens to the date as far as I can see so I am thinking
that
>> when and if "I" add a date I might enter me 1887 me standing for
>> myself or
>> SD 1887 SD being my initials letting me know that the date was
>> entirely my
>> idea and in notes I may explain how "I" came to pick that date. I have
>> not
>> tried any reports using this technique so I have no idea how or if it
>> will
>> work out yet.
>>
>> Rootsweb.com Admin: {for} Caplinger, Duncan, Forsythe,
>> Mounce, Schoonover, Tyler, Vanscoy, Wilmoth, Zane
>>
>> Sandra Tyler Duncan
>> [EMAIL PROTECTED]
>> http://www.gencircles.com/users/purplevw1/1
>> *-* THE GREATEST*-*
>> http://www.progenealogists.com/genealogysleuthb.htm
>> ================================
>> Work like you don't need the money.
>> Love like you've never been hurt.
>> Dance like nobody's looking.
>> ----- Original Message -----
>> From: "Ron Klotz Zellhoefer" <[EMAIL PROTECTED]>
>> To: <[email protected]>
>> Sent: Friday, May 27, 2005 6:54 AM
>> Subject: Re: [LegacyUG] learning from mistakes
>>
>>
>>> Hi,
>>> I'm coming into this thread late, but ...
>>> When posting an individual with no known birthdate, I *always enter
>>> something* for birthdate.
>>> Perhaps most frequently is finding/posting a parent, where e.g.
>>> "[childbirthdate]-30" may be appropriate, posted as e.g. "Est 1848".
>>> Two benefits --
>>> first that Legacy will then mark the individual as dead at an
>>> appropriate
>>> future date
>>> second it's most helpful in e.g. Index View for sorting individuals
>>> and/or
>>> in just plain seeing *something* which might help one "recognize" that
>>> individual, especially amongst many with the same name!
>>> HTL
>>> RonKZ
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
