Why not use “Abt” or “a” for short data entry?
C.G. Ouimet Kingston ON From: Howard Cady [mailto:[email protected]] Sent: July 10, 2014 05:12 PM To: [email protected] Subject: Re: [LegacyUG] Legacy Family Tree - Virtual User's Group Meeting this Friday, July 11 (Dates, Searching and Tagging) Sherry, Perhaps I was not clear enough about my concern for “Est” as a prefix for dates. Legacy version 7 was clear that “Est” is an allowed prefix in addition to “Abt”, “Cir”, and “Cal” for indicating uncertainty. However, Legacy 8 is unclear. “Est” is no longer a listed option under Options>Customize>Dates, nor is it mentioned as a prefix under Help>Index>Dates Approximated>Prefixes, nor is it mentioned under Help>Index>Dates Entering an allowed prefix. It is true that it still works as a distinct prefix from “Abt” etc., but I, for one, want it retained as one of the shades of uncertainty. Howard From: Sherry/Support <mailto:[email protected]> Sent: Thursday, July 10, 2014 12:50 PM To: [email protected] Subject: Re: [LegacyUG] Legacy Family Tree - Virtual User's Group Meeting this Friday, July 11 (Dates, Searching and Tagging) Why do you both think that Est isn't accepted? I'm using it just fine and it shows in the Help file as acceptable. I don't get any Potential Problem warning, nor an error with Options > Customize 5.5 selected. In the Dates topic under "Approximating Dates" it says When entering an estimated date, use an appropriate prefix, such as: Estimated or Est About or Abt Before or Bef After or Aft It could be that Geoff just accidentally left it out of the syllabus. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Jul 10, 2014 at 11:18 AM, Jay 1FamilyTree <[email protected]> wrote: Howard, I have had no problems with using Cir, or Abt. instead of est. I have now replaced EVERY date that is not complete with some sort of descriptor like abt, aft, bef, bet, cir, cal. and I am extremely pleased with the results as it make all the sorting so much better (I have a rather large database with many similar names. ) I try stick to some patterns, like using Cir for a birth of a spouse based only upon the birth of their spouse. I use aft YYYY in a marriage date as 18 yrs after the youngest spouse. I use bef YYYY in a marriage date when I know the birth year of a child I use aft YYYY in a birth date when I know the marriage year of the parents I use bef YYYY in a death date when I see their spouse is widowed on a census and I use abt YYYY when using a census date as a birth date. Since may other software programs do not recognize EST. I look forward to fewer errors in exchanging ged files. Jay On Thu, Jul 10, 2014 at 9:33 AM, Howard Cady <[email protected]> wrote: Goeff, I note in your Webinar notes that “Est = Estimated” has been dropped from allowed dates. One of the main reasons for my switching to Legacy was this descriptor. I use it especially when I know the birth dates of one or more children and only the names of parents, grand parents, gg-parents etc. This allows for keeping people in the correct order and century (or better). I hope it is not planned to drop this feature. Howard Cady Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
