Re: [LegacyUG] Still battling with Emdash errors

[Jennifer Crockett]

Cathy

I am pretty much satisfied I found most of the instances in various locations.  
I tried it with spaces before and or after the “\emdash” and picked up some 
with each of those variations. 

The only problem seemed to be an emdash sandwiched between two uppercase 
surnames, with no spaces. As I went through search and replace, I made a note 
of those it wasn’t picking up (if I saw them next to ones it was picking up) 
and then went back to those people and fixed them.

Thank you very much for bearing with me. You have helped me immensely.

Jennifer


From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Cathy Pinner
Sent: Monday, 10 July 2017 5:04 PM
To: Legacy User Group 
Subject: Re: [LegacyUG] Still battling with Emdash errors

Jennifer,

Good to hear that you've made progress.
I know it shows as /'97 but that's not the way or the main way it's actually 
being saved in the database (I think I've said this before - search for \emdash 
- but maybe that was to someone else)

If "\emdash " isn't finding it try without the space on the end though when 
there weren't spaces in my test, it was finding them.

You may find you end up with xxx-- xxx instead of xxx--xxx but it's easy to 
search and replace on "-- " and replace with "--" if necessary.

Cathy

Jennifer Crockett wrote:


Cathy

There is progress here! I was searching for /'97 not emdash.

Here is an example of what happened when I searched as you suggested, "\emdash 
" without the quotes, in Citation-Text:

GOLDEN WEDDING
WENCK\emdash SAILOR \emdash  On 2 nd August, 1899. at Ipswich, by Rev. Ryan, 
Ernest, third Son of the late Mr. and Mrs. R. Wenck, Minden, to Emily, second 
Daughter of the late Mr. and Mrs. A. Sailor Lowood.

Legacy picked up the second instance, but not the first. Have you any idea why? 
It may have something to do with no space after WENCK or before SAILOR.

Jennifer

-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Cathy Pinner
Sent: Monday, 10 July 2017 3:58 PM
To: mailto:LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Still battling with Emdash errors

Jennifer,

I'm sorry this is causing you so much trouble.
I seem to be able to use search and replace You have to search for "\emdash " 
without the quotes.
This is replacing the \'97 which shows in the Notes when an emdash has been 
saved with no space on either side.

I'm not sure if this works on every field where you may ha ve emdashes.
It works in Birth Notes (so presumably other vital event notes), General Notes 
and Citation text.
Strangely emdashes are surviving in Citation detail.

I'm not sure whether the way an emdash has been saved has changed over time.

I haven't been entering more but haven't bothered too much about the ones I 
have as I haven't needed good publishing output for awhile.

Let me know if this doesn't work and I'll try again.

Cathy





Jennifer Crockett
Monday, 10 July 2017 12:55 PM

The biggest nightmare I have had in going form Legacy 7.5 to Legacy 9
(I skipped 8) has to be the issue of Legacy not converting Emdash code
properly in most instances.

I have been able to correct some with Search and Replace, but not the
majority.

The missed ones in Search and Replace are where the Emdash  did not
have a space before or after. For example, SMITH”emdash”JONES; or
“emdash”SMITH

Since I know most instances come from a particular Master Source, did
a Show List for that source and came up with a list of nearly 1000
names. I made a search list and tagged the names, and as I was going
through the list untagged when I had checked and if necessary
corrected all the ’97 to a double ordinary dash.

I had gone through about 30 when I realised that the Marriage Notes
were not on the Individual I was looking at, so I have to start again.
Can someone please help my tired brain by suggesting a step by step
plan of action. Obviously I can’t get through 1000 in one session, so
it has to be a list somewhere I can pick up and stop when I have the
time and inclination.

If there are any users still on 7.5 who are considering updating to
Legacy 8 or 9, especially if you use Trove in Australia for sources
and not es – be aware this will also happen to you. (Unless Legacy
fixes the problem. I has been in existence apparently since Legacy 8,
so don’t hold your breath.)

Jennifer




-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Cathy Pinner]

Chris,
On your initial problem. Something is going on with your computer. 
Legacy 8 runs fine under Windows 10 without any compatibility settings. 
Without finding out what that is, you'll likely have problems with 
Legacy 9 as well.


On not upgrading to Legacy 9 until the problems are all sorted. Legacy 9 
already has less problems than Legacy 8 in the areas they share. There 
are some problems in new features but most people aren't encountering 
them just as most people aren't encountering the many bugs in Legacy 8, 
some of which have been fixed in 9 now but not in 8.


Wanting a transfer of data between programs and online trees etc without 
loss is just not going to happen. Different programs and different 
online trees have differing features - that's why they exist. It's the 
differences that lead people to prefer one over the other.


It's remarkable that the old Gedcom standard with a few tweaks does such 
a good job but even from Legacy to the same version of Legacy via Gedcom 
loses a few things, most visible is that SourceWriter sources are 
converted to Basic.


Cathy
Legacy Tester


Chris Hill 
Tuesday, 11 July 2017 3:59 AM

Having been a committee member for the design and implementation of 
the EDI standards in Europe, in the mid 1980-1990s,  I am well aware 
of the issues of getting a standard format. We ended up with a lot of 
optional records that most people ignored or did not need, and equally 
with the issue of a business decided that he did want them and 
insisted that you provide them.


Hopefully, we will get to a basic structure which everyone will 
support and with only a few, if any, non-mandatory fields.


Regards

Chris

*From:*LegacyUserGroup 
[mailto:legacyusergroup-boun...@legacyusers.com] *On Behalf Of 
*Michael Feldman

*Sent:* 10 July 2017 20:22
*To:* Legacy User Group 
*Subject:* Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

Hi all,

Chris Hill wrote:


[snip]

A worthy ideal overall, but "no exceptions" is unlikely to happen in 
practice. The computing world is filled with technical standards of 
one kind or another; anyone who works in, or near, a standards 
committee know this is like herding cats. And even after a standard is 
adopted, some cats will wander off in their own direction anyway 
(which is why standards are always revised periodically, to bring 
exceptions into the fold, then the process starts again). It's human 
nature (and, often, business nature as well).


[ASIDE] The evolution of character-set standards is a good example. I 
think the discussion here of the em-dash problems is a manifestation 
of this. "Back in the day" (the fifties), a character was represented 
as six bits. Of course this limited the total number of characters to 
64, which is why the early computers printed everything as UPPER CASE 
-- no room for lower case in the character set. In recent decades, 
we've gone to 7 bits, 8 bits, and beyond, to try to accommodate all 
countries' alphabets and now, even, emojis. Google "number of bits in 
an emoji" for character-set fun and games.


[back to GEDCOM] It'll be interesting to see what FHISO comes up with...

Just my $0.02.:-)

Mike Feldman

Michael Feldman 
Tuesday, 11 July 2017 3:22 AM
Hi all,

Chris Hill wrote:

[snip]
A worthy ideal overall, but "no exceptions" is unlikely to happen in 
practice. The computing world is filled with technical standards of 
one kind or another; anyone who works in, or near, a standards 
committee know this is like herding cats. And even after a standard is 
adopted, some cats will wander off in their own direction anyway 
(which is why standards are always revised periodically, to bring 
exceptions into the fold, then the process starts again). It's human 
nature (and, often, business nature as well).


[ASIDE] The evolution of character-set standards is a good example. I 
think the discussion here of the em-dash problems is a manifestation 
of this. "Back in the day" (the fifties), a character was represented 
as six bits. Of course this limited the total number of characters to 
64, which is why the early computers printed everything as UPPER CASE 
-- no room for lower case in the character set. In recent decades, 
we've gone to 7 bits, 8 bits, and beyond, to try to accommodate all 
countries' alphabets and now, even, emojis. Google "number of bits in 
an emoji" for character-set fun and games.


[back to GEDCOM] It'll be interesting to see what FHISO comes up with...

Just my $0.02.:-)

Mike Feldman
Chris Hill 
Tuesday, 11 July 2017 2:54 AM

In theory, if everyone assumes that the GEDCOM is a standardised 
format. Unfortunately, it is not, and was released in 1996 for the 
5.5.1 version. There was a XML version designed in 2002 which never 
went anywhere. Look at https://en.wikipedia.org/wiki/GEDCOM.


Anyone, including Legacy, has the ability to add their 

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Michael Feldman]

  
  
Hi all,

Chris Hill wrote:


[snip]

  
 
The
Family History Information Standards Organisation (FHISO)
was started in 2012 and has just released its very
first draft standards for public comment, at the end of
June. Something that I need to review.
Hopefully,
if we can get everyone supporting a single standard, with no
exceptions, we will then be able to transfer data with no
loss.
  

A worthy ideal overall, but "no exceptions" is unlikely to happen in
practice. The computing world is filled with technical standards of
one kind or another; anyone who works in, or near, a standards
committee know this is like herding cats. And even after a standard
is adopted, some cats will wander off in their own direction anyway
(which is why standards are always revised periodically, to bring
exceptions into the fold, then the process starts again). It's human
nature (and, often, business nature as well).

[ASIDE] The evolution of character-set standards is a good example.
I think the discussion here of the em-dash problems is a
manifestation of this. "Back in the day" (the fifties), a character
was represented as six bits. Of course this limited the total number
of characters to 64, which is why the early computers printed
everything as UPPER CASE -- no room for lower case in the character
set. In recent decades, we've gone to 7 bits, 8 bits, and beyond, to
try to accommodate all countries' alphabets and now, even, emojis.
Google "number of bits in an emoji" for character-set fun and games.

[back to GEDCOM] It'll be interesting to see what FHISO comes up
with...

Just my $0.02.:-)

Mike Feldman
  


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Donna Newell]

I agree with you.  Some of us are happy with 8 and shouldn't have to change. 
And yes I agree they are adding to many dodads to the program, in my opinion it 
makes it more unstable.  Yes I have issues with 8.  Purchased 9 but delayed 
installing it for same reason.  What is the rush!

Sent from my iPad

> On Jul 10, 2017, at 11:08 AM, Gene Wheeler  wrote:
> 
> That just seems to introduce another set of issues! I've purchased v.9, but 
> am holding off using it until the problems all get cleared up. I think LFT is 
> maybe getting too complicated to design and use all the new features. IMHO, 
> they should continue to support v.8 for those of us who would rather have a 
> solid, reliable tool and still offer v.9 to those who have more patience to 
> deal with it's issues and can't wait to use the new features.
> 
> Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as 
> the preferred version, and still run v.9 to learn its intricacies before 
> adopting it to replace v.8.
> 
> Gene
> 
>> On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH  wrote:
>> you nee dto upgrade to latest versions!!
>> 
>> 
>> Bob Suddath
>> rasudd...@msn.com
>> denversuddaths.homestead.com
>> 
>> 
>> From: LegacyUserGroup  on behalf of 
>> Chris Hill 
>> Sent: Monday, July 10, 2017 8:35 AM
>> To: LegacyUserGroup@LegacyUsers.com
>> Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
>>  
>> This is for information.
>>  
>> I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft 
>> and running the Symantec Norton Anti-Virus.
>>  
>> About a month ago it got updated to V8.0.0.602. That then likes to display a 
>> prompt about upgrading to Legacy 9. Hit Close to ship out and you get a 
>> Run-Tine Error 75 message and the program closes. Eventually resolved that 
>> as a program combability issue, having raised it as an formal issue and got 
>> pointed at the collection of possible causes.
>>  
>> I have now been updated to V8.0.0.604 and the same issue occurred. This time 
>> I completely removed and reinstalled, and still got the same issue. Ran the 
>> program compatibility checks and Windows decided that it needed to be in 
>> mode Windows XP (SP2) and it now works.
>>  
>> But Legacy 8 came out in 2013, so it should have been compatible to Win 
>> Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and 
>> .604 versions that have this issue – certainly I have seen no issues with 
>> previous versions. So what have Legacy developers changed for these versions 
>> to make then incompatible or have they forgotten to tell the installer to 
>> make them needing to be in Win XP SP2. The other alternative is that I am up 
>> to date on Microsoft .NET to level 4.6, and have 4.7 waiting for 
>> installation.
>>  
>> Regards
>>  
>> Chris
>>  
>>  
>> 
>> --
>> 
>> LegacyUserGroup mailing list
>> LegacyUserGroup@legacyusers.com
>> To manage your subscription and unsubscribe 
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>> 
> 
> -- 
> 
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe 
> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] DNA Tests

[Marli Yoder]

Thank you for the help
Marli Yoder
A & M Farms 2173 LLC
Eureka & Sturgeon Missouri

On Mon, Jul 10, 2017 at 11:25 AM, Michele/Support <
mich...@legacyfamilytree.com> wrote:

> Autosomal DNA is not reported in the same way as yDNA or mtDNA
> (mitochondrial) are.  yDNA and mtDNA results are easy to enter because they
> have values attached to specific fields so Legacy provides a place to enter
> this information.  Autosomal is different.  If you download your raw data
> you will see a text file approx 8MB in size with thousands of values.
>
>
>
> Most people create DNA events to record their DNA info.  You can add the
> testing company, the date tested, the kit number (if applicable) the
> GEDmatch number (if applicable) and any other notes.  You can screenshot
> your ethnicity percentages and attach that to the event media gallery.  Be
> aware though that your ethnicity percentages will change from time to time
> as the companies run their algorithms against additional reference samples.
>
>
>
> You can also use tagging and/or Hashtags to keep track of your DNA (I use
> Hashtags).
>
>
>
> Legacy's main purpose is not DNA tracking.  For that you need to use the
> Chromosome browsers that are built into 23andMe and FTDNA (two of the
> companies that offer chromosome browsers).  Ancestry.com, MyHeritage and
> LivingDNA do not have chromosome browsers so it is a bit harder there. You
> can also use the free program Genome Mate Pro https://genomemate.org/
> which is an advanced chromosome browser and you can also upload your raw
> data to the GEDmatch website https://www.gedmatch.com
>
>
>
> Michele Simmons Lewis, CG
>
> Legacy Family Tree
>
> mich...@legacyfamilytree.com
>
> www.legacyfamilytree.com
>
>
>
> Certified Genealogist is a registered trademark and the designation CG is
> a service mark of the Board for Certification of Genealogists®, used under
> license by Board certificants who meet competency standards.
>
>
>
> *From:* LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] *On
> Behalf Of *Marli Yoder
> *Sent:* Monday, July 10, 2017 12:03 PM
> *To:* Legacy Users Group 
> *Subject:* [LegacyUG] DNA Tests
>
>
>
> I have V.9, latest build. Question is how do I add the test results from
> My Heritage DNA test.? Looked at the list under the DNA symbol, and did not
> see the one I took. (Manage two other tests from them also).
>
>
>
> I also did family tree DNA (not finished yet) on my self and two other
> family members.
>
>
>
> Will be doing Ancestry as well on some of my family.
>
>
>
> Am I missing a step? I downloaded the results from My Heritage . Unzipped
> them.. now what?
>
> (Good to know it shows my great-aunt and I really are related :) )
>
>
>
> Marli Yoder
>
> A & M Farms 2173 LLC
>
> Eureka & Sturgeon Missouri
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Leonard J. McCown]

Chris, I thought that the GEDCOM format was
supposed to help transfer your data from one
program to another with the basic information
traveling. I moved from Family Roots, to Personal
Ancestral File, to Ancestral Quest with no
problems in the past. Leonard

 

-

__
___

 

Leonard J. McCown, Irving, Texas -- McCown Family
History

217 West 14th Street, Irving, Texas 75060-5903

972-254-7952

  leon...@mccown.org --
 http://www.mccown.org

People will not look forward to posterity who
never look backward to

their ancestors. -- Edmund Burke, 1790

__
___

 

 

From: LegacyUserGroup
[mailto:legacyusergroup-boun...@legacyusers.com]
On Behalf Of Chris Hill
Sent: Monday, July 10, 2017 11:18 AM
To: 'Legacy User Group'

Subject: Re: [LegacyUG] Problem with V8.0.0.602
and V8.0.0.604

 

That is a different question. I think I would find
the hashtags useful, and possibly a couple of the
other additions, but most of them are, to me,
pointless.

 

The one thing that I do want, and will never get,
is a standardised interface API between the
different genealogy programs and the online
systems, so that we can accurately and easily
transfer information with no loss.

 

Regards

 

Chris

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Bob Austen]

Hi Gene,

If you hold off using v9 until ALL the issues are resolved then you may never 
get to use it.  I have been using v9 since the day it was released and have had 
no more issues than with v8.  Legacy has been quick to respond to any problems 
and, I’m sure, will continue to do so.

 

You can run v8 & v9 side by side. V9 overwrites the v8 files (without warning) 
so make a copy of all the v8 files first, install v9, then rename the v8 files. 
 V9 is not compatible with v8 so running them side-by-side is really not 
practical as they will two separate, non-compatible, databases.  I kept the 
option to run v8 as I still help others who haven’t (didn’t) upgrade but I have 
never had to go back to it.  Just make the switch to v9.

 

  Bob Austen

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Gene Wheeler
Sent: Monday, July 10, 2017 9:09 AM
To: Legacy User Group
Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

 

That just seems to introduce another set of issues! I've purchased v.9, but am 
holding off using it until the problems all get cleared up. I think LFT is 
maybe getting too complicated to design and use all the new features. IMHO, 
they should continue to support v.8 for those of us who would rather have a 
solid, reliable tool and still offer v.9 to those who have more patience to 
deal with it's issues and can't wait to use the new features.

Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as 
the preferred version, and still run v.9 to learn its intricacies before 
adopting it to replace v.8.

 

Gene

 

On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH  wrote:

you nee dto upgrade to latest versions!!

 

Bob Suddath 

rasudd...@msn.com

denversuddaths.homestead.com

 

  _  

From: LegacyUserGroup  on behalf of 
Chris Hill 
Sent: Monday, July 10, 2017 8:35 AM
To: LegacyUserGroup@LegacyUsers.com
Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 

 

This is for information.

 

I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and 
running the Symantec Norton Anti-Virus.

 

About a month ago it got updated to V8.0.0.602. That then likes to display a 
prompt about upgrading to Legacy 9. Hit Close to ship out and you get a 
Run-Tine Error 75 message and the program closes. Eventually resolved that as a 
program combability issue, having raised it as an formal issue and got pointed 
at the collection of possible causes.

 

I have now been updated to V8.0.0.604 and the same issue occurred. This time I 
completely removed and reinstalled, and still got the same issue. Ran the 
program compatibility checks and Windows decided that it needed to be in mode 
Windows XP (SP2) and it now works.

 

But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, 
Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 
versions that have this issue – certainly I have seen no issues with previous 
versions. So what have Legacy developers changed for these versions to make 
then incompatible or have they forgotten to tell the installer to make them 
needing to be in Win XP SP2. The other alternative is that I am up to date on 
Microsoft .NET to level 4.6, and have 4.7 waiting for installation.

 

Regards

 

Chris

 

 


--

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] DNA Tests

[Michele/Support]

Autosomal DNA is not reported in the same way as yDNA or mtDNA (mitochondrial) 
are.  yDNA and mtDNA results are easy to enter because they have values 
attached to specific fields so Legacy provides a place to enter this 
information.  Autosomal is different.  If you download your raw data you will 
see a text file approx 8MB in size with thousands of values.

 

Most people create DNA events to record their DNA info.  You can add the 
testing company, the date tested, the kit number (if applicable) the GEDmatch 
number (if applicable) and any other notes.  You can screenshot your ethnicity 
percentages and attach that to the event media gallery.  Be aware though that 
your ethnicity percentages will change from time to time as the companies run 
their algorithms against additional reference samples. 

 

You can also use tagging and/or Hashtags to keep track of your DNA (I use 
Hashtags).

 

Legacy's main purpose is not DNA tracking.  For that you need to use the 
Chromosome browsers that are built into 23andMe and FTDNA (two of the companies 
that offer chromosome browsers).  Ancestry.com, MyHeritage and LivingDNA do not 
have chromosome browsers so it is a bit harder there. You can also use the free 
program Genome Mate Pro https://genomemate.org/ which is an advanced chromosome 
browser and you can also upload your raw data to the GEDmatch website 
https://www.gedmatch.com

 

Michele Simmons Lewis, CG

Legacy Family Tree

mich...@legacyfamilytree.com   

www.legacyfamilytree.com    

 

Certified Genealogist is a registered trademark and the designation CG is a 
service mark of the Board for Certification of Genealogists®, used under 
license by Board certificants who meet competency standards.

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Marli Yoder
Sent: Monday, July 10, 2017 12:03 PM
To: Legacy Users Group 
Subject: [LegacyUG] DNA Tests

 

I have V.9, latest build. Question is how do I add the test results from My 
Heritage DNA test.? Looked at the list under the DNA symbol, and did not see 
the one I took. (Manage two other tests from them also).

 

I also did family tree DNA (not finished yet) on my self and two other family 
members. 

 

Will be doing Ancestry as well on some of my family.  

 

Am I missing a step? I downloaded the results from My Heritage . Unzipped 
them.. now what? 

(Good to know it shows my great-aunt and I really are related :) )

 

Marli Yoder

A & M Farms 2173 LLC

Eureka & Sturgeon Missouri

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Chris Hill]

That is a different question. I think I would find the hashtags useful, and
possibly a couple of the other additions, but most of them are, to me,
pointless.

 

The one thing that I do want, and will never get, is a standardised
interface API between the different genealogy programs and the online
systems, so that we can accurately and easily transfer information with no
loss.

 

Regards

 

Chris

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On
Behalf Of ROBERT A SUDDATH
Sent: 10 July 2017 16:47
To: Legacy User Group 
Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

 

you nee dto upgrade to latest versions!!

 

Bob Suddath 

rasudd...@msn.com  

denversuddaths.homestead.com

 

  _  

From: LegacyUserGroup  > on behalf of Chris Hill
 >
Sent: Monday, July 10, 2017 8:35 AM
To: LegacyUserGroup@LegacyUsers.com 

Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 

 

This is for information.

 

I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft
and running the Symantec Norton Anti-Virus.

 

About a month ago it got updated to V8.0.0.602. That then likes to display a
prompt about upgrading to Legacy 9. Hit Close to ship out and you get a
Run-Tine Error 75 message and the program closes. Eventually resolved that
as a program combability issue, having raised it as an formal issue and got
pointed at the collection of possible causes.

 

I have now been updated to V8.0.0.604 and the same issue occurred. This time
I completely removed and reinstalled, and still got the same issue. Ran the
program compatibility checks and Windows decided that it needed to be in
mode Windows XP (SP2) and it now works.

 

But Legacy 8 came out in 2013, so it should have been compatible to Win
Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and
.604 versions that have this issue - certainly I have seen no issues with
previous versions. So what have Legacy developers changed for these versions
to make then incompatible or have they forgotten to tell the installer to
make them needing to be in Win XP SP2. The other alternative is that I am up
to date on Microsoft .NET to level 4.6, and have 4.7 waiting for
installation.

 

Regards

 

Chris

 

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Gene Wheeler]

That just seems to introduce another set of issues! I've purchased v.9, but
am holding off using it until the problems all get cleared up. I think LFT
is maybe getting too complicated to design and use all the new features.
IMHO, they should continue to support v.8 for those of us who would rather
have a solid, reliable tool and still offer v.9 to those who have more
patience to deal with it's issues and can't wait to use the new features.

Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8
as the preferred version, and still run v.9 to learn its intricacies before
adopting it to replace v.8.

Gene

On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH 
wrote:

> you nee dto upgrade to latest versions!!
>
>
> Bob Suddath
> rasudd...@msn.com
> denversuddaths.homestead.com
>
>
> --
> *From:* LegacyUserGroup  on
> behalf of Chris Hill 
> *Sent:* Monday, July 10, 2017 8:35 AM
> *To:* LegacyUserGroup@LegacyUsers.com
> *Subject:* [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
>
>
> This is for information.
>
>
>
> I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by
> Microsoft and running the Symantec Norton Anti-Virus.
>
>
>
> About a month ago it got updated to V8.0.0.602. That then likes to display
> a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a 
> *Run-Tine
> Error 75* message and the program closes. Eventually resolved that as a
> program combability issue, having raised it as an formal issue and got
> pointed at the collection of possible causes.
>
>
>
> I have now been updated to V8.0.0.604 and the same issue occurred. This
> time I completely removed and reinstalled, and still got the same issue.
> Ran the program compatibility checks and Windows decided that it needed to
> be in mode *Windows XP (SP2)* and it now works.
>
>
>
> But Legacy 8 came out in 2013, so it should have been compatible to Win
> Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and
> .604 versions that have this issue – certainly I have seen no issues with
> previous versions. So what have Legacy developers changed for these
> versions to make then incompatible or have they forgotten to tell the
> installer to make them needing to be in Win XP SP2. The other alternative
> is that I am up to date on Microsoft .NET to level 4.6, and have 4.7
> waiting for installation.
>
>
>
> Regards
>
>
>
> Chris
>
>
>
>
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] DNA Tests

[Marli Yoder]

I have V.9, latest build. Question is how do I add the test results from My
Heritage DNA test.? Looked at the list under the DNA symbol, and did not
see the one I took. (Manage two other tests from them also).

I also did family tree DNA (not finished yet) on my self and two other
family members.

Will be doing Ancestry as well on some of my family.

Am I missing a step? I downloaded the results from My Heritage . Unzipped
them.. now what?
(Good to know it shows my great-aunt and I really are related :) )

Marli Yoder
A & M Farms 2173 LLC
Eureka & Sturgeon Missouri
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[ROBERT A SUDDATH]

you nee dto upgrade to latest versions!!


Bob Suddath
rasudd...@msn.com
denversuddaths.homestead.com



From: LegacyUserGroup  on behalf of 
Chris Hill 
Sent: Monday, July 10, 2017 8:35 AM
To: LegacyUserGroup@LegacyUsers.com
Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604


This is for information.



I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and 
running the Symantec Norton Anti-Virus.



About a month ago it got updated to V8.0.0.602. That then likes to display a 
prompt about upgrading to Legacy 9. Hit Close to ship out and you get a 
Run-Tine Error 75 message and the program closes. Eventually resolved that as a 
program combability issue, having raised it as an formal issue and got pointed 
at the collection of possible causes.



I have now been updated to V8.0.0.604 and the same issue occurred. This time I 
completely removed and reinstalled, and still got the same issue. Ran the 
program compatibility checks and Windows decided that it needed to be in mode 
Windows XP (SP2) and it now works.



But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, 
Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 
versions that have this issue – certainly I have seen no issues with previous 
versions. So what have Legacy developers changed for these versions to make 
then incompatible or have they forgotten to tell the installer to make them 
needing to be in Win XP SP2. The other alternative is that I am up to date on 
Microsoft .NET to level 4.6, and have 4.7 waiting for installation.



Regards



Chris




-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] Problem with V8.0.0.602 and V8.0.0.604

[Chris Hill]

This is for information.

 

I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft
and running the Symantec Norton Anti-Virus.

 

About a month ago it got updated to V8.0.0.602. That then likes to display a
prompt about upgrading to Legacy 9. Hit Close to ship out and you get a
Run-Tine Error 75 message and the program closes. Eventually resolved that
as a program combability issue, having raised it as an formal issue and got
pointed at the collection of possible causes.

 

I have now been updated to V8.0.0.604 and the same issue occurred. This time
I completely removed and reinstalled, and still got the same issue. Ran the
program compatibility checks and Windows decided that it needed to be in
mode Windows XP (SP2) and it now works.

 

But Legacy 8 came out in 2013, so it should have been compatible to Win
Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and
.604 versions that have this issue - certainly I have seen no issues with
previous versions. So what have Legacy developers changed for these versions
to make then incompatible or have they forgotten to tell the installer to
make them needing to be in Win XP SP2. The other alternative is that I am up
to date on Microsoft .NET to level 4.6, and have 4.7 waiting for
installation.

 

Regards

 

Chris

 

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Error problem, need help

[Michele/Support]

Dennis, 
I have updated the bug report with this information :)   I am also answering 
your email with your other questions. 

 

 

Michele Simmons Lewis, CG

Legacy Family Tree

  mich...@legacyfamilytree.com 

  www.legacyfamilytree.com  

 

Certified Genealogist is a registered trademark and the designation CG is a 
service mark of the Board for Certification of Genealogists®, used under 
license by Board certificants who meet competency standards.

 

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Dennis Murphy
Sent: Monday, July 10, 2017 9:30 AM
To: Legacy User Group 
Subject: Re: [LegacyUG] Error problem, need help

 

Thank you Cathy, you saved the day!

 

Indeed it was a missing story that caused the error and it would seem that 
those numbers in parentheses are a clue to the Legacy location. (1, 18835) The 
error occurs in my RIN #1 though I'm not sure about the 18835 as I do not have 
that many stories in my file. But when I went to RIN #1 and tried to open the 
story, I got my old familiar error message. I deleted the link and then I was 
able to extract my family file from my master database with no problems or 
errors.

 

Many Kudos Cathy 

 

PS: if other list members have the same situation and get errors, here's a 
little tip: When you go to back up the extracted file be sure to close the 
other file or you will get "Backup Error 527" Close the master or larger file 
and it will go without incident.

 

murf

 

On Sun, Jul 9, 2017 at 10:59 PM, Cathy Pinner  > wrote:

Dennis,

Have you added any Stories?
A couple of people on Facebook have had a similar error message doing different 
things to you and each other.
They both tracked it to a problem with a seemingly blank Story location.
I can't force it to happen so I'm not sure what is causing it.

I can just suggest checking Stories. The error occurs as well when you try to 
open the problem Story.
The numbers in brackets may be RIN numbers.

Do let Support or me (as a Legacy Tester with an interest in this particular 
issue) know if this is the problem.

Cathy

George wrote:




Dennis:

Contact support. I had a problem a couple of weeks ago and could not 
open my file.  Support was able to fix it for me.

George

*From:*LegacyUserGroup 
[mailto:legacyusergroup-bounces@legacyusers 
 . com] *On Behalf Of *Dennis 
Murphy
*Sent:* July 9, 2017 7:46 PM
*To:* LegacyUserGroup@legacyusers.com  
*Subject:* [LegacyUG] Error problem, need help

I have a mater database of 75K+ from which I am trying to extract my 
family line of about 54K.. I never had any problem doing so in the 
nearly 25 years I have been using Legacy until NOW!

I keep getting the message "Location 18835 not found" followed by a 
series of numbers in parentheses such as (1, 19846) with the latter 
number often different.

The screen instructs me to run the Repair/Check program under File 
Maintenance, which I keep doing to no avail and no fix. Afterwards I 
get "ERROR 3021 - no current record" I then looked up the Error number 
in the Legacy Help menu and followed all suggestions. Sill I get the 
same results.

In desperation I tried the last suggested fix, which was to export the 
file as a Gedcom, but that brought me back once again to the "Location 
18835 not found." So now I'm really stumped.

Does anyone know what that means? Is it referencing a geological 
location or a person's data., marriage, event. etc.??

murf

In short, any ideas how to fix this and save 30 years of work?


--

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com  
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Error problem, need help

[Dennis Murphy]

Thank you Cathy, you saved the day!

Indeed it was a missing story that caused the error and it would seem that
those numbers in parentheses are a clue to the Legacy location. (1, 18835)
The error occurs in my RIN #1 though I'm not sure about the 18835 as I do
not have that many stories in my file. But when I went to RIN #1 and tried
to open the story, I got my old familiar error message. I deleted the link
and then I was able to extract my family file from my master database with
no problems or errors.

Many Kudos Cathy 

PS: if other list members have the same situation and get errors, here's a
little tip: When you go to back up the extracted file be sure to close the
other file or you will get "Backup Error 527" Close the master or larger
file and it will go without incident.

murf

On Sun, Jul 9, 2017 at 10:59 PM, Cathy Pinner  wrote:

> Dennis,
>
> Have you added any Stories?
> A couple of people on Facebook have had a similar error message doing
> different things to you and each other.
> They both tracked it to a problem with a seemingly blank Story location.
> I can't force it to happen so I'm not sure what is causing it.
>
> I can just suggest checking Stories. The error occurs as well when you try
> to open the problem Story.
> The numbers in brackets may be RIN numbers.
>
> Do let Support or me (as a Legacy Tester with an interest in this
> particular issue) know if this is the problem.
>
> Cathy
>
> George wrote:
>
>
> Dennis:
>
> Contact support. I had a problem a couple of weeks ago and could not
> open my file.  Support was able to fix it for me.
>
> George
>
> *From:*LegacyUserGroup
> [mailto:legacyusergroup-bounces@legacyusers. com] *On Behalf Of *Dennis
> Murphy
> *Sent:* July 9, 2017 7:46 PM
> *To:* LegacyUserGroup@legacyusers.com
> *Subject:* [LegacyUG] Error problem, need help
>
> I have a mater database of 75K+ from which I am trying to extract my
> family line of about 54K.. I never had any problem doing so in the
> nearly 25 years I have been using Legacy until NOW!
>
> I keep getting the message "Location 18835 not found" followed by a
> series of numbers in parentheses such as (1, 19846) with the latter
> number often different.
>
> The screen instructs me to run the Repair/Check program under File
> Maintenance, which I keep doing to no avail and no fix. Afterwards I
> get "ERROR 3021 - no current record" I then looked up the Error number
> in the Legacy Help menu and followed all suggestions. Sill I get the
> same results.
>
> In desperation I tried the last suggested fix, which was to export the
> file as a Gedcom, but that brought me back once again to the "Location
> 18835 not found." So now I'm really stumped.
>
> Does anyone know what that means? Is it referencing a geological
> location or a person's data., marriage, event. etc.??
>
> murf
>
> In short, any ideas how to fix this and save 30 years of work?
>
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Temple submissions

[Michael Slater]

Marlyne,

In FamilySearch there is the option to choose the ordinances you would like
to do. You do not have to print all of them, you can select those that you
want to do.  The difficulty that Legacy is experiencing is not a Legacy
problem but a change in protocol in FamilySearch that is causing difficulty
at the moment. Dont be dissapointed, Legacy is still the best genealogy
software there is. (I am not an employee, just a very satisfied user)

Regards
Michael

On 9 July 2017 at 17:29, Marlyne Natali via LegacyUserGroup <
legacyusergroup@legacyusers.com> wrote:

> The original message to the list is in the attachment.
>
> This action is required because of the DMARC Reject/Quarantine Policy
> imposed by some email providers. Users who want to send messages
> without conversion to attachments should use a different email address
> for their subscription.
>
> Known providers for free email accounts whose emails do not require
> this conversion include gmail.com and hotmail.com.  Many other email
> providers will also work but you will have to give them a try.
>
> -- Forwarded message --
> From: Marlyne Natali 
> To: "legacyusergroup@legacyusers.com" 
> Cc:
> Bcc:
> Date: Sun, 9 Jul 2017 21:28:52 + (UTC)
> Subject: Temple submissions
> I used to be able to share temple work by going to "Go To Ordinance
> Tracking Center." There I could choose which ordinances I wanted to share.
>
> Now this link takes me directly to FamilySearch.org and I cannot choose
> the ordinances I want to share, I have to print out the whole card.
>
> I have grandchildren who can only do baptisms and confirmations. They tend
> to forget to pick up the card after finishing these ordinance, or they lose
> the card at school, in their packpacks, etc. I do not want to send a whole
> card of ordinaces where they cannot so all of them.
>
> Am I not looking in the right place to find where I can just choose the
> ordinances I want to share, or has Legacy removed this with their updates?
> If so, I am disappointed that I will no longer be able to share these
> ordinances with my grandchildren who live in several states. I would prefer
> to send cards out with only the ordinance I want to have done by them,
> because my family members seem to lose track of the cards whether done or
> not. I know I can reprint cards, but lately that has not worked, and a few
> other people have told me the same thing when family members did not return
> cards and the ordinance area shows the work not done.
>
> Marlyne Natali
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Temple submissions

[Michael Slater]

David Turley, nothing to do with Legacy. Do you have a relative who was on
a mission in Paraguay some years ago?

On 9 July 2017 at 19:48, David Turley  wrote:

> Marlyne
> Legacy will allow you to print cards with only the Baptisms and
> Confirmations.
> Go to your list of Reserved Temple Ordinances.
> Select the individuals whose ordinances you want printed.by ticking the
> box on the left next to their name.
> When you have finished selecting the individuals, you will see 3 options
> near the top of the screen.
> Select Print, then select Print Family Ordinance Cards.
> The next screen will allow you to select the ordinances you want printed
> by unselecting the ones you DON'T want printed.
> You should now see a screen that will show cards with only the Baptism and
> Confirmation boxes empty.
> Now select Continue.
> You should now see a Print Request screen. Select Continue at the bottom.
> To print them, select the printer icon on the far right side of the ribbon
> at the top.
> Now select Print at the bottom left. When you close his screen, you will
> be asked whether or not the cards printed.
> Good luck
>
> On Sun, Jul 9, 2017 at 4:55 PM, Brian Kelly  wrote:
>
>> The tracking centre is not working in Legacy right now because of changes
>> made by the familysearch website. Until those changes are finalized the
>> redirect to FamilySearch will have to remain. Once the changes at
>> FamilySearch settle down Legacy will be able to re-institute the Tracking
>> Centre.
>>
>> Brian Kelly
>>
>> On 09-Jul-17 5:30 PM, Marlyne Natali via LegacyUserGroup wrote:
>>
>>> Subject: Temple submissions
>>> From: Marlyne Natali 
>>> Date: 09-Jul-17 5:28 PM
>>> To: "legacyusergroup@legacyusers.com" 
>>>
>>> I used to be able to share temple work by going to "Go To Ordinance
>>> Tracking Center." There I could choose which ordinances I wanted to share.
>>> Now this link takes me directly to FamilySearch.org and I cannot choose
>>> the ordinances I want to share, I have to print out the whole card.
>>> I have grandchildren who can only do baptisms and confirmations. They
>>> tend to forget to pick up the card after finishing these ordinance, or they
>>> lose the card at school, in their packpacks, etc. I do not want to send a
>>> whole card of ordinaces where they cannot so all of them.
>>> Am I not looking in the right place to find where I can just choose the
>>> ordinances I want to share, or has Legacy removed this with their updates?
>>> If so, I am disappointed that I will no longer be able to share these
>>> ordinances with my grandchildren who live in several states. I would prefer
>>> to send cards out with only the ordinance I want to have done by them,
>>> because my family members seem to lose track of the cards whether done or
>>> not. I know I can reprint cards, but lately that has not worked, and a few
>>> other people have told me the same thing when family members did not return
>>> cards and the ordinance area shows the work not done.
>>>   Marlyne Natali
>>>
>>
>> ---
>> This email has been checked for viruses by AVG.
>> http://www.avg.com
>>
>>
>> --
>>
>> LegacyUserGroup mailing list
>> LegacyUserGroup@legacyusers.com
>> To manage your subscription and unsubscribe
>> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
>> Archives at:
>> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>>
>
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

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

[Michele/Support]

The fact that the case is changed is in our bug tracker.  It is issue #5829 and 
it has been assigned to a programmer to be fixed.  The fix will appear in an 
update but there is no way to predict when that will be.

 

 

Michele Simmons Lewis, CG

Legacy Family Tree

  mich...@legacyfamilytree.com 

  www.legacyfamilytree.com  

 

Certified Genealogist is a registered trademark and the designation CG is a 
service mark of the Board for Certification of Genealogists®, used under 
license by Board certificants 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 
Subject: 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 changes it to "est" 
with lower case first letter.  I am a stickler for continuity in my file and 
all other date prefix's have the first letter capitalized.  

 

If the prefix is recognized, it should allow the capitalization as it does on 
all other prefix's..and I must add that in previous versions right up to 
and including Legacy 8 update prior to this last one, it had no problem 
changing Estimated, estimated, Est, est to .Est. So something happened in 
the latest update to Legacy 8.

 

I have made the choice to not wait for any programming change as I assume that 
Legacy 9 has staff concentrating on those updates and problem reports rather 
than looking backwards at this time.  I will upgrade to Legacy 9 later this 
year but in the meantime I have done a search and replace for est to Abt. My 
Ancestry file will also be changed as was suggested by some bright person 
(Thank you) and will move forward with my merge of those file when they are in 
sync.

 

Thanks to everyone who responded..this is why I love Legacy.

 

Lucy Abbott

Mill Creek, WA, USA

 

 

 

 

On Friday, July 7, 2017 6:56 PM, Michele Lewis  > wrote:

 

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 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







 

 


 

 


--

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers. com  
To manage your subscription and unsubscribe http://legacyusers.com/ 
mailman/listinfo/ legacyusergroup_legacyusers. com 
 
Archives at:
http://www.mail-archive.com/ legacyusergroup@legacyusers. com/ 
 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com  
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Still battling with Emdash errors

[Cathy Pinner]

Jennifer,

Good to hear that you've made progress.
I know it shows as /'97 but that's not the way or the main way it's 
actually being saved in the database (I think I've said this before - 
search for \emdash - but maybe that was to someone else)


If "\emdash " isn't finding it try without the space on the end though 
when there weren't spaces in my test, it was finding them.


You may find you end up with xxx-- xxx instead of xxx--xxx but it's easy 
to search and replace on "-- " and replace with "--" if necessary.


Cathy

Jennifer Crockett wrote:


Cathy

There is progress here! I was searching for /'97 not emdash.

Here is an example of what happened when I searched as you suggested, 
"\emdash " without the quotes, in Citation-Text:


GOLDEN WEDDING
WENCK\emdash SAILOR \emdash On 2nd August, 1899. at Ipswich, by Rev. 
Ryan, Ernest, third Son of the late Mr. and Mrs. R. Wenck, Minden, to 
Emily, second Daughter of the late Mr. and Mrs. A. Sailor Lowood.


Legacy picked up the second instance, but not the first. Have you any 
idea why? It may have something to do with no space after WENCK or 
before SAILOR.


Jennifer

-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] 
On Behalf Of Cathy Pinner

Sent: Monday, 10 July 2017 3:58 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Still battling with Emdash errors

Jennifer,

I'm sorry this is causing you so much trouble.
I seem to be able to use search and replace You have to search for 
"\emdash " without the quotes.
This is replacing the \'97 which shows in the Notes when an emdash has 
been saved with no space on either side.


I'm not sure if this works on every field where you may have emdashes.
It works in Birth Notes (so presumably other vital event notes), 
General Notes and Citation text.

Strangely emdashes are surviving in Citation detail.

I'm not sure whether the way an emdash has been saved has changed over 
time.


I haven't been entering more but haven't bothered too much about the 
ones I have as I haven't needed good publishing output for awhile.


Let me know if this doesn't work and I'll try again.

Cathy





Jennifer Crockett
Monday, 10 July 2017 12:55 PM

The biggest nightmare I have had in going form Legacy 7.5 to Legacy 9
(I skipped 8) has to be the issue of Legacy not converting Emdash code
properly in most instances.

I have been able to correct some with Search and Replace, but not the
majority.

The missed ones in Search and Replace are where the Emdash did not
have a space before or after. For example, SMITH”emdash”JONES; or
“emdash”SMITH

Since I know most instances come from a particular Master Source, did
a Show List for that source and came up with a list of nearly 1000
names. I made a search list and tagged the names, and as I was going
through the list untagged when I had checked and if necessary
corrected all the ’97 to a double ordinary dash.

I had gone through about 30 when I realised that the Marriage Notes
were not on the Individual I was looking at, so I have to start again.
Can someone please help my tired brain by suggesting a step by step
plan of action. Obviously I can’t get through 1000 in one session, so
it has to be a list somewhere I can pick up and stop when I have the
time and inclination.

If there are any users still on 7.5 who are considering updating to
Legacy 8 or 9, especially if you use Trove in Australia for sources
and notes – be aware this will also happen to you. (Unless Legacy
fixes the problem. I has been in existence apparently since Legacy 8,
so don’t hold your breath.)

Jennifer




-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Still battling with Emdash errors

[Jennifer Crockett]

Cathy

There is progress here! I was searching for /'97 not emdash.

Here is an example of what happened when I searched as you suggested, "\emdash 
" without the quotes, in Citation-Text:

GOLDEN WEDDING 
WENCK\emdash SAILOR \emdash  On 2nd August, 1899. at Ipswich, by Rev. Ryan, 
Ernest, third Son of the late Mr. and Mrs. R. Wenck, Minden, to Emily, second 
Daughter of the late Mr. and Mrs. A. Sailor Lowood.

Legacy picked up the second instance, but not the first. Have you any idea why? 
It may have something to do with no space after WENCK or before SAILOR.

Jennifer

-Original Message-
From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of Cathy Pinner
Sent: Monday, 10 July 2017 3:58 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Still battling with Emdash errors

Jennifer,

I'm sorry this is causing you so much trouble.
I seem to be able to use search and replace You have to search for "\emdash " 
without the quotes.
This is replacing the \'97 which shows in the Notes when an emdash has been 
saved with no space on either side.

I'm not sure if this works on every field where you may have emdashes.  
It works in Birth Notes (so presumably other vital event notes), General Notes 
and Citation text.
Strangely emdashes are surviving in Citation detail.

I'm not sure whether the way an emdash has been saved has changed over time.

I haven't been entering more but haven't bothered too much about the ones I 
have as I haven't needed good publishing output for awhile.

Let me know if this doesn't work and I'll try again.

Cathy



> Jennifer Crockett 
> Monday, 10 July 2017 12:55 PM
>
> The biggest nightmare I have had in going form Legacy 7.5 to Legacy 9 
> (I skipped 8) has to be the issue of Legacy not converting Emdash code 
> properly in most instances.
>
> I have been able to correct some with Search and Replace, but not the 
> majority.
>
> The missed ones in Search and Replace are where the Emdash  did not 
> have a space before or after. For example, SMITH”emdash”JONES; or 
> “emdash”SMITH
>
> Since I know most instances come from a particular Master Source, did 
> a Show List for that source and came up with a list of nearly 1000 
> names. I made a search list and tagged the names, and as I was going 
> through the list untagged when I had checked and if necessary 
> corrected all the ’97 to a double ordinary dash.
>
> I had gone through about 30 when I realised that the Marriage Notes 
> were not on the Individual I was looking at, so I have to start again.
> Can someone please help my tired brain by suggesting a step by step 
> plan of action. Obviously I can’t get through 1000 in one session, so 
> it has to be a list somewhere I can pick up and stop when I have the 
> time and inclination.
>
> If there are any users still on 7.5 who are considering updating to 
> Legacy 8 or 9, especially if you use Trove in Australia for sources 
> and notes – be aware this will also happen to you. (Unless Legacy 
> fixes the problem. I has been in existence apparently since Legacy 8, 
> so don’t hold your breath.)
>
> Jennifer



-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/