Re: [LegacyUG] Still battling with Emdash errors

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.

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

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

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

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

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

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

Re: [LegacyUG] DNA Tests

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

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

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 -

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

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

Re: [LegacyUG] DNA Tests

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

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

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

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

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:

[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

Re: [LegacyUG] Error problem, need help

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

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

Re: [LegacyUG] Temple submissions

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

Re: [LegacyUG] Temple submissions

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

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

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

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

Re: [LegacyUG] Still battling with Emdash errors

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