Re: [LegacyUG] Legacy 8 - date change after latest update

September 2017 12:12 PM To: Legacy User Group <legacyusergroup@legacyusers.com>; Susie Zada <sz...@zades.com.au> Subject: Re: [LegacyUG] Legacy 8 - date change after latest update Do you know that for most NSW BDM's, you can now zero in on the precise date by trial and error by testi

Re: [LegacyUG] Legacy 8 - date change after latest update

Hi Graham, Yes - have done this on a number of my own family but most of the NSW and Vic BDMs I have were researched and collected over the last 30 to 40 years - that wasn't an option back then! :-( Regards ... Susie Z September 29, 2017 12:11 PM, "Graham Lambert"

Re: [LegacyUG] Legacy 8 - date change after latest update

To: legacyusergroup@legacyusers.com Subject: Re: [LegacyUG] Legacy 8 - date change after latest update I suppose I could call those calculated dates but since I only use a year in those kind of calculations I prefer about 1834 instead of Calc 1834. I reserve Calc for dates when I can figure out the day month

Re: [LegacyUG] Legacy 8 - date change after latest update

: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of JV Leavitt Sent: Thursday, September 28, 2017 9:39 PM To: Legacy User Group <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Legacy 8 - date change after latest update Brian, are you not basing th

Re: [LegacyUG] Legacy 8 - date change after latest update

...@legacyusers.com] On Behalf Of Brian Kelly Sent: Friday, 29 September 2017 7:13 AM To: legacyusergroup@legacyusers.com Subject: Re: [LegacyUG] Legacy 8 - date change after latest update I suppose I could call those calculated dates but since I only use a year in those kind of calculations I prefer about

Re: [LegacyUG] Legacy 8 - date change after latest update

I suppose I could call those calculated dates but since I only use a year in those kind of calculations I prefer about 1834 instead of Calc 1834. I reserve Calc for dates when I can figure out the day month and year. Brian Kelly On 28-Sep-17 3:38 PM, JV Leavitt wrote: Brian, are you not

Re: [LegacyUG] Legacy 8 - date change after latest update

Brian, are you not basing the date on a calculation? Why not use the term Calculated instead? If I see the term About, I don't automatically think it is meant to mean plus or minus a year or two. My experience tells me that yes, I know it can very often mean plus or minus a year or two, or--

Re: [LegacyUG] Legacy 8 - date change after latest update

p-boun...@legacyusers.com] *On > Behalf Of *cf6e2...@opayq.com > *Sent:* Thursday, September 28, 2017 8:09 PM > *To:* legacyusergroup@legacyusers.com > *Subject:* Re: [LegacyUG] Legacy 8 - date change after latest update > > > > Estimate and about are synonym as far as I'm conce

Re: [LegacyUG] Legacy 8 - date change after latest update

To: legacyusergroup@legacyusers.com Subject: Re: [LegacyUG] Legacy 8 - date change after latest update Estimate and about are synonym as far as I'm concerned. I always try to go back to the source since that's what it's based on. On Thu, Sep 28, 2017 at 10:44 AM, Brian Kelly [Masked] < <

Re: [LegacyUG] Legacy 8 - date change after latest update

acyusergroup-boun...@legacyusers.com] On >> Behalf Of JV Leavitt >> Sent: Thursday, September 28, 2017 4:38 PM >> To: Legacy User Group <legacyusergroup@legacyusers.com> >> Subject: Re: [LegacyUG] Legacy 8 - date change after latest update >> >> Does anyon

Re: [LegacyUG] Legacy 8 - date change after latest update

gacyusers.com> Subject: Re: [LegacyUG] Legacy 8 - date change after latest update Does anyone know what the term "About" means when used with a date? Everyone seems to have a different idea about the level of credibility to give it. Many think it must be within a few years, and don't t

Re: [LegacyUG] Legacy 8 - date change after latest update

I think it is defined differently for each one of us, and that's okay as long as we are consistent and we let our "audience it's accurate, but not exact.  I use estimate when it is a wild guess just to get me in the right area then it becomes to me +/- 25 years. Elmer On 9/28/2017 10:37 AM,

Re: [LegacyUG] Legacy 8 - date change after latest update

- date change after latest update On 28-Sep-17 03:37 PM, JV Leavitt wrote: > I'm very disappointed that the term Estimated or Est is not included > in Legacy's Date Prefix options. I thought there would be a workaround for this, in that for Options 5.7 in the box for "Displayed"

Re: [LegacyUG] Legacy 8 - date change after latest update

On 28-Sep-17 03:37 PM, JV Leavitt wrote: I'm very disappointed that the term Estimated or Est is not included in Legacy's Date Prefix options. I thought there would be a workaround for this, in that for Options 5.7 in the box for "Displayed" next to "Circa, Cir or C" one could type "Est" and

Re: [LegacyUG] Legacy 8 - date change after latest update

. Anne -Original Message- From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of JV Leavitt Sent: Thursday, September 28, 2017 4:38 PM To: Legacy User Group <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Legacy 8 - date change after latest update

Re: [LegacyUG] Legacy 8 - date change after latest update

Does anyone know what the term "About" means when used with a date? Everyone seems to have a different idea about the level of credibility to give it. Many think it must be within a few years, and don't think of it as being a wild guess (which so often turns out to be the case), but I'm not

Re: [LegacyUG] Legacy 8 - date change after latest update

nts who meet competency standards. From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Lucy Abbott Sent: Sunday, July 9, 2017 2:52 PM To: Legacy User Group <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Legacy 8 - date change after latest upda

Re: [LegacyUG] Legacy 8 - date change after latest update

In response to Michele Lewis and Ms Pinter, you state that Legacy does in fact recognize Est as a valid prefix to a date, however that is not what Legacy is "doing". I understand that the underlying programming see's "Estimated" as valid "input" BUT will not let that full version stand, it

Re: [LegacyUG] Legacy 8 - date change after latest update

A GEDCOM file is a plain text file but the lines are organized in a special way and include key words that let genealogy programs understand the contents. Each program then stores the contents in their own special data format when they import the GEDCOM file. You can open any GEDCOM file with

Re: [LegacyUG] Legacy 8 - date change after latest update

Est is not a prefix in the options menu but Legacy does "see" it as valid. There is a bug in our tracker about this asking the programmers to put Est in the options menu with the rest of the valid prefixes. On Jul 2, 2017 2:43 PM, "Lucy Abbott" wrote: > I have always used

Re: [LegacyUG] Legacy 8 - date change after latest update

Est is a valid date format in Legacy even though it isn't listed at Options-Customise 5.7 There's no need to change it. Cathy Lucy Abbott Saturday, 8 July 2017 4:00 AM OK, had not thought of setting up the Gedcom from Ancestry, changing all the Est to Abt, doing

Re: [LegacyUG] Legacy 8 - date change after latest update

OK, had not thought of setting up the Gedcom from Ancestry, changing all the Est to Abt, doing the same with my existing Legacy file before doing the merge. Not exactly what I want but it would work and save time. Never done a search and replace but going to make a duplicate file and try this

Re: [LegacyUG] Legacy 8 - date change after latest update

Lucy Abbott, Remember to save the file as PLAIN text with the ".ged" file extension, or it will include "garbage" you do not want from what I have been told in the past. Jay Ingalls On 7/3/2017 3:51 PM, Jenny M Benson wrote: On 03-Jul-17 07:59 PM, Lucy Abbott wrote: Give me an option

Re: [LegacyUG] Legacy 8 - date change after latest update

On 03-Jul-17 07:59 PM, Lucy Abbott wrote: Give me an option here that I can use. I want to stay with Est because there is no way that I know of to change all the ones on Ancestry and I had planned on downloading a Gedcom and merging that file with my Legacy file once I have done all the

Re: [LegacyUG] Legacy 8 - date change after latest update

All I know is that I would type est and the system would change it to Est as soon as I moved on to the place field. Now it will not do that even though I have said "do not change what I type".  That order only appears to work on the name fields.  When I type "Estimated" completely, it knows

Re: [LegacyUG] Legacy 8 - date change after latest update

Est has never been one of the date prefixes in Legacy. I went back to Legacy 7.5 and the only prefixes there are: Abt, After, Bef, Between, Cal, Cir and B.C. Those are the same prefixes listed in 9.0. Legacy 9.0 did change the prefixes to lowercase by default. I just changed mine to initial

[LegacyUG] Legacy 8 - date change after latest update

I have always used Est rather than Abt. Since I did the latest update to Legacy 8, it has changed all my Est to est.  Looking at date options, it appears that Estimated is no longer a valid prefix and it won't capitalize for that reason.  This is a lot of people that I have to change to Abt,