Lucy Abbott <mailto:[email protected]>
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 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 on existing Legacy file.
Your comments on making my Gedcom a Text file have me confused. I
normally just ask Ancestry to make a Gedcom, did not know I should
make some adjustment to it or that I could even do something
different. Feel free to email me directly with some help on this if
you would.
Thx for the solution for the changing of the files, really appreciate.
Lucy Abbott
Mill Creek, WA, USA
On Monday, July 3, 2017 4:28 PM, "J.M. "Jay" Ingalls"
<[email protected]> wrote:
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 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 research at that
>> site. Without this correction, many more hours will need to be used
>> on the merge. My merge is scottish names and 60% are duplicate type
>> names due to naming conventions so hours and hours are needed for the
>> merge and this has me frustrated thinking of how many more hours will
>> be needed to change the dates headings.
>
> If it turns out that you DO have to change "est" to something else, it
> needn't take hours. If you open your Gedcom as a Legacy file you
> could use the Search & Replace function to change all the instances of
> "est" in each Date field. Granted, not a single-step option, but
> wouldn't take too long. In fact, a Gedcom being text file I think you
> could probably do the Search & Replace in the Gedcom with WP program.)
>
--
LegacyUserGroup mailing list
[email protected] <mailto:[email protected]>
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
J.M. "Jay" Ingalls <mailto:[email protected]>
Tuesday, 4 July 2017 7:22 AM
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
Jenny M Benson <mailto:[email protected]>
Tuesday, 4 July 2017 4:51 AM
If it turns out that you DO have to change "est" to something else, it
needn't take hours. If you open your Gedcom as a Legacy file you
could use the Search & Replace function to change all the instances of
"est" in each Date field. Granted, not a single-step option, but
wouldn't take too long. In fact, a Gedcom being text file I think you
could probably do the Search & Replace in the Gedcom with WP program.)
Lucy Abbott <mailto:[email protected]>
Tuesday, 4 July 2017 2:59 AM
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 enough to change it to "est" so there is
programming there somewhere that recognizes the word estimated. With
my background knowledge it appears I should be able to work with this
and get my Est back.
Sooooo, tried to find any option that would tell it to make the first
letter in a field a capital. Could not find any that would work with
the date fields. Have gone through all the options and marked every
field "initial caps" but none of them work for the date fields.
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 research at that site. Without
this correction, many more hours will need to be used on the merge. My
merge is scottish names and 60% are duplicate type names due to naming
conventions so hours and hours are needed for the merge and this has
me frustrated thinking of how many more hours will be needed to change
the dates headings.
Please help ...............
Lucy M Abbott
Mill Creek, WA, USA
On Sunday, July 2, 2017 3:19 PM, Brian Kelly <[email protected]> wrote:
Interesting that the help mentions Est and estimated but the date
settings do not have an option for that term.
Brian Kelly
On 02-Jul-17 5:32 PM, Bert van Kootwijk wrote:
>
> From the helpfile ( topic 1077)
>
> *Approximating Dates*
>
> If you have a birth or marriage date for an individual, you can
> approximate many other missing dates. In general you can estimate that
> a man was married when he was 25 and a woman when she was 21. You can
> then estimate that their first child was born one year later and that
> subsequent children were born every two years after that. For example,
> if a couple was married in 1863, you can estimate that the man was born
> in 1838, the woman in 1842, their first child in 1864 and the second
> child in 1866. As another example, if a woman was born in 1800, you
can
> estimate that she was married in 1821, her husband was born in 1796 and
> their first child was born in 1822.
>
> When entering an estimated date, use an appropriate prefix, such as:
>
> Estimated or Est
>
> About or Abt
>
> Before or Bef
>
> After or Aft
>
>
> So it looks as Legacy recognize "Est".. No idea why it not works.
>
>
> Bert
>
>
>
> Op 2-7-2017 om 22:56 schreef Brian Kelly:
>> 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 Caps and they appear to hold in Options and
>> displayed correctly on screen. I did not test the reports to see how
>> date prefixes are used there.
>>
>> Brian Kelly
>>
>> On 02-Jul-17 2:41 PM, Lucy Abbott wrote:
>>> 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, which I don't want to do. Plus it means that
>>> all my Ancestry data has to be changed in order for me to have the
>>> files match.
>>>
>>> Why is Est no longer a valid prefix for a date ? Do I have to roll
>>> back to the prior update to be able to use again ? Can I roll back
>>> to the prior update ?
>>>
>>> Lucy M. Abbott
>>> Mill Creek, Washington, USA
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> ---
>> This email has been checked for viruses by AVG.
>> http://www.avg.com <http://www.avg.com/>
>>
>>
>
>
> ---
> Dit e-mailbericht is gecontroleerd op virussen met Avast
antivirussoftware.
> https://www.avast.com/antivirus
>
>
--
LegacyUserGroup mailing list
[email protected] <mailto:[email protected]>
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
