Re: [LegacyUG] Please forget that previous post.
Michele et al, Please refer to Legacy News archives for 9/8/2017 and 9/14/2017 for the special offers mentioned by Goeff for MyHeritage subscriptions. So far all I Have needed to renew is persistence on the telephone with MyHeritage. LFT seems to have a short memory and has not helped me on this renewal problem. Howard Cady From: Michele Lewis Sent: Thursday, May 9, 2019 5:19 AM To: 'Legacy User Group' Subject: Re: [LegacyUG] Please forget that previous post. Normally I wouldn’t comment on anything MyHeritage but I will this time. Legacy is a completely separate entity. MyHeritage’s sales and tech support is totally separate from ours. There is no communication between the two. We know absolutely nothing about their prices, sales, deals, etc. Complaining to us doesn’t help your cause because we have no say so or influence over what they do or they don’t do. Any complaints you have need to go to them, not us. Michele Simmons Lewis, CG® Legacy Educator Legacy Family Tree/MyHeritage mich...@legacyfamilytree.com www.legacyfamilytree.com From: LegacyUserGroup On Behalf Of Gloria DeSousa Sent: Thursday, May 9, 2019 7:10 AM To: Legacy User Group Subject: Re: [LegacyUG] Please forget that previous post. I wouldn't count on MyHeritage sticking to their promise of a discounted rate. I've had to make numerous phone calls all last year and then was harassed with 4 unsolicited phone calls from the same very pushy sales rep in MyHeritage last October until I stopped answering phone calls from myheritage. He was trying to sell me some package deal of 5 years, and of course, he was unaware of the discounted rate. I could go on with how my account was reverted to the basic level once again earlier this year, but my reason for posting is what has Legacy done about it? Does Legacy know about this? Gloria On Wed, May 8, 2019 at 12:59 PM Hogrooter . wrote: I had a similar problem with MyHeritage forgetting about their earlier subscription offer. After several attempts via email I finally called them by phone. The first individual I spoke to appeared to be a basic customer service agent who wanted me to renew at their full rates. After some discussion he transferred me to someone who appeared to be more senior and knew about the low lifetime subscriptions. The man confirmed my discounted rate and said he had included this in my record for use in future years. It took some persistence to get everything straight but did work out in the end. (We will see what happens when my next renewal is due.) Regards, Dean Adams Virus-free. www.avast.com On Wed, May 8, 2019 at 11:02 AM Ian Macaulay wrote: I just found out the address. If you log in from a different machine you get a notice and it contains their snail mail addy.. So I now have it and it is now logged in my Address book. Ian -- ICMac Sales: Hobby consultant (1986r.) Office hours: 10:00 Am - 5:00 PM most days Macaulay Genealogy Family Matters Ian Macaulayof Carp, Ontario -- 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/ -- Dean -- 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] Potential GEDCOM Error
Cathy,
If a person is set to Living = No because there is a “Cause of Death” in
Medical Notes then it is no longer an option to be changed on the Individual
Information screen. That is why I had to find an alternate route to set living
to YES.
Howard
From: Cathy Pinner
Sent: Monday, November 6, 2017 8:32 PM
To: Legacy User Group
Subject: Re: [LegacyUG] Potential GEDCOM Error
Howard,
I trust your brother is getting excellent care in the Hospice.
Thanks for pointing out what you were using. It's not often I learn of a
feature in Legacy I've not been aware of. I use Advanced Set Living quite often
but didn't know you could change this setting for a group. I obviously don't
use the Name List/Search List often enough and when I do, I know what I'm
looking for and don't see the other options.
I certainly wouldn't think of using it for an individual or two. Easier to do
it on their Individual Information screen where you can find the problem if you
can't change the setting.
In fact, I can't think of a use for it the way I use Legacy which is no doubt
why I don't know about it. It would perhaps be helpful when importing a gedcom
where the living setting was a mess. Set everyone without death information to
living and then use Advance d set living to set obviously deceased people to
dead.
Cathy
Howard Cady wrote:
Cathy,
Somewhere in the help listings for Legacy I found a method for
resetting the Living Yes/No for a tagged set of individuals. I used
tag 8 for the brother as the only tagged individual in my file. Then
used the sequence of selections View/ Name List/ Options/ Set Living/
All Individuals Tagged on 8/ Set Living = Yes to try to return the
brother to life. I often got a message that 1 Individual had been
reset, but found on his Individual Information screen that he was
still dead.
This brother is in Hospice Care and I had entries under Sources -
Death Cause and Medical Notes listing his anticipated “Cause of Death”
without realizing that a Sourced Note could actually be fatal without
entering anything for Death/Burial information. It took me several
attempts at finding and removi ng information, labels, or sources to
bring him back to life.
I don’t think I had a problem that will occur often. Your initial
suggestion was the important clue for fixing my problem and I don’t
think further work is needed.
Howard
*From:* Cathy Pinner
*Sent:* Sunday, November 5, 2017 9:55 PM
*To:* Legacy User Group
*Subject:* Re: [LegacyUG] Potential GEDCOM Error
Howard,
I'm glad it's sorted but you shouldn't have to remove Medical Notes
unless you'd put them in Cause of Death or sourced them as Cause of
Death. I just retested this and adding Cause of Death or sources for
it doesn't change the Living status either.
I don't know what you mean by "View-Set Living".
If you mean Tools - Advanced Set Living - well it wouldn't help as it
is badly named - it means set the living flag to deceased if the
person couldn't still be alive based on surrounding individuals. The
unofficial title i s Intellimurder ;)
If you mean setting the flag on the Individual Information screen - it
would reset to deceased if one of the fields associated with death was
filled.
Cathy
Howard Cady wrote:
Cathy,
You were correct as to the cause of my problem (individual marked as
deceased). Fi xing the problem was harder. The “View-Set Living” reset
kept returning “fixed” but the Individual Information screen kept
returning “Deceased” for several attempts. Deleting Medical Notes and
Medical Note Sources was my final fix that was required to get him
alive. Thanks for steering me to the solution.
Howard Cady
*From:* Cathy Pinner
*Sent:* Saturday, November 4, 2017 6:55 PM
*To:* Legacy User Group
*Subject:* Re: [LegacyUG] Potential GEDCOM Error
Howard,
You don't need LTools for this and I'd be very wary of using LTools
beyond Legacy 7.
For t his particular case, you just need to look at his Individual
Information screen and see.
For others you may want to check, you can use Legacy Detailed Search.
Individual - Birth Date - after -
AND
Individual - Living - equal to - NO
Cathy
Howard Cady wrote:
Cathy, Thanks for the information that removing everything from
death/burial/sources wouldn’t restore “deceased” to “living”. I will
search for “deceased” and dig out Ltools and look when I have time –
but not before this reply. It is also possible that I might have
checked his deceased box at one time and then reversed that check.
Howard
*From:* Cathy Pinner
*Sent:* Friday, Nov ember 3, 2017 6:26 PM
*To:* Legacy User Group
*Subject:* Re: [LegacyUG] Potential GEDCOM Error
Have you checked that he's not been accidentally marked as deceased in
your file? It's easy to
Re: [LegacyUG] Potential GEDCOM Error
Cathy,
Somewhere in the help listings for Legacy I found a method for resetting the
Living Yes/No for a tagged set of individuals. I used tag 8 for the brother as
the only tagged individual in my file. Then used the sequence of selections
View/ Name List/ Options/ Set Living/ All Individuals Tagged on 8/ Set Living =
Yes to try to return the brother to life. I often got a message that 1
Individual had been reset, but found on his Individual Information screen that
he was still dead.
This brother is in Hospice Care and I had entries under Sources - Death Cause
and Medical Notes listing his anticipated “Cause of Death” without realizing
that a Sourced Note could actually be fatal without entering anything for
Death/Burial information. It took me several attempts at finding and removing
information, labels, or sources to bring him back to life.
I don’t think I had a problem that will occur often. Your initial suggestion
was the important clue for fixing my problem and I don’t think further work is
needed.
Howard
From: Cathy Pinner
Sent: Sunday, November 5, 2017 9:55 PM
To: Legacy User Group
Subject: Re: [LegacyUG] Potential GEDCOM Error
Howard,
I'm glad it's sorted but you shouldn't have to remove Medical Notes unless
you'd put them in Cause of Death or sourced them as Cause of Death. I just
retested this and adding Cause of Death or sources for it doesn't change the
Living status either.
I don't know what you mean by "View-Set Living".
If you mean Tools - Advanced Set Living - well it wouldn't help as it is badly
named - it means set the living flag to deceased if the person couldn't still
be alive based on surrounding individuals. The unofficial title is
Intellimurder ;)
If you mean setting the flag on the Individual Information screen - it would
reset to deceased if one of the fields associated with death was filled.
Cathy
Howard Cady wrote:
Cathy,
You were correct as to the cause of my problem (individual marked as
deceased). Fi xing the problem was harder. The “View-Set Living” reset
kept returning “fixed” but the Individual Information screen kept
returning “Deceased” for several attempts. Deleting Medical Notes and
Medical Note Sources was my final fix that was required to get him
alive. Thanks for steering me to the solution.
Howard Cady
*From:* Cathy Pinner
*Sent:* Saturday, November 4, 2017 6:55 PM
*To:* Legacy User Group
*Subject:* Re: [LegacyUG] Potential GEDCOM Error
Howard,
You don't need LTools for this and I'd be very wary of using LTools
beyond Legacy 7.
For this particular case, you just need to look at his Individual
Information screen and see.
For others you may want to check, you can use Legacy Detailed Search.
Individual - Birth Date - after -
AND
Individual - Living - equal to - NO
Cathy
Howard Cady wrote:
Cathy, Thanks for the information that removing everything from
death/burial/sources wouldn’t restore “deceased” to “living”. I will
search for “deceased” and dig out Ltools and look when I have time –
but not before this reply. It is also possible that I might have
checked his deceased box at one time and then reversed that check.
Howard
*From:* Cathy Pinner
*Sent:* Friday, Nov ember 3, 2017 6:26 PM
*To:* Legacy User Group
*Subject:* Re: [LegacyUG] Potential GEDCOM Error
Have you checked that he's not been accidentally marked as deceased in
your file? It's easy to do. Adding anything in death or burial field
or adding a source to them will switch the Living indicator. Removing
it doesn't switch the indicator back.
Cathy
Howard Cady wrote:
I used Legacy 9 version 198 to prepare an GEDCOM (import to Ancestry
version) of my wife's bloodline (only her relatives) with privacy
(only names for living people). Everything was as expected except for
her living brother where the exported file treated him as deceased. My
wife and all living descendants were properly exported as names only.
A deceased older sister was properly exported as deceased. Have others
noticed this potential error?
Howard Cady
--
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] Potential GEDCOM Error
Cathy, You were correct as to the cause of my problem (individual marked as deceased). Fixing the problem was harder. The “View-Set Living” reset kept returning “fixed” but the Individual Information screen kept returning “Deceased” for several attempts. Deleting Medical Notes and Medical Note Sources was my final fix that was required to get him alive. Thanks for steering me to the solution. Howard Cady From: Cathy Pinner Sent: Saturday, November 4, 2017 6:55 PM To: Legacy User Group Subject: Re: [LegacyUG] Potential GEDCOM Error Howard, You don't need LTools for this and I'd be very wary of using LTools beyond Legacy 7. For this particular case, you just need to look at his Individual Information screen and see. For others you may want to check, you can use Legacy Detailed Search. Individual - Birth Date - after - AND Individual - Living - equal to - NO Cathy Howard Cady wrote: Cathy, Thanks for the information that removing everything from death/burial/sources wouldn’t restore “deceased” to “living”. I will search for “deceased” and dig out Ltools and look when I have time – but not before this reply. It is also possible that I might have checked his deceased box at one time and then reversed that check. Howard *From:* Cathy Pinner *Sent:* Friday, Nov ember 3, 2017 6:26 PM *To:* Legacy User Group *Subject:* Re: [LegacyUG] Potential GEDCOM Error Have you checked that he's not been accidentally marked as deceased in your file? It's easy to do. Adding anything in death or burial field or adding a source to them will switch the Living indicator. Removing it doesn't switch the indicator back. Cathy Howard Cady wrote: I used Legacy 9 version 198 to prepare an GEDCOM (import to Ancestry version) of my wife's bloodline (only her relatives) with privacy (only names for living people). Everything was as expected except for her living brother where the exported file treated him as deceased. My wife and all living descendants were properly exported as names only. A deceased older sister was properly exported as deceased. Have others noticed this potential error? Howard Cady --- - -- 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] Potential GEDCOM Error
Cathy, Thanks for the information that removing everything from death/burial/sources wouldn’t restore “deceased” to “living”. I will search for “deceased” and dig out Ltools and look when I have time – but not before this reply. It is also possible that I might have checked his deceased box at one time and then reversed that check. Howard From: Cathy Pinner Sent: Friday, November 3, 2017 6:26 PM To: Legacy User Group Subject: Re: [LegacyUG] Potential GEDCOM Error Have you checked that he's not been accidentally marked as deceased in your file? It's easy to do. Adding anything in death or burial field or adding a source to them will switch the Living indicator. Removing it doesn't switch the indicator back. Cathy Howard Cady wrote: I used Legacy 9 version 198 to prepare an GEDCOM (import to Ancestry version) of my wife's bloodline (only her relatives) with privacy (only names for living people). Everything was as expected except for her living brother where the exported file treated him as deceased. My wife and all living descendants were properly exported as names only. A deceased older sister was properly exported as deceased. Have others noticed this potential error? Howard Cady -- -- 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] Potential GEDCOM Error
I used Legacy 9 version 198 to prepare an GEDCOM (import to Ancestry version) of my wife's bloodline (only her relatives) with privacy (only names for living people). Everything was as expected except for her living brother where the exported file treated him as deceased. My wife and all living descendants were properly exported as names only. A deceased older sister was properly exported as deceased. Have others noticed this potential error? Howard Cady -- 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 Tip of the Day
Michele, Thanks for posting the "Tip of the Day" I am one of the non FaceBook users of Legacy FT. This tip makes me want to see your previous Tips. I hope you will be able to do this and continue to cross post to the Legacy Users Group. -Original Message- From: Michele/Support Sent: Monday, April 24, 2017 7:40 AM To: 'Legacy User Group' Subject: [LegacyUG] Legacy Tip of the Day I am going to start cross posting the tips that I post on the Legacy User Group Facebook page so that those of you that are not on Facebook you will see them too. TIP OF THE DAY (Legacy Staff) - Another Easter Egg feature Open someone's Individual's Information screen (this is where you actually add data to someone) Click the FamilySearch ID LABEL. If the person does not have an FSID number already in the field, you will get FamilySearch's record search results page. If they do have an FSID entered you will go directly to their Family Tree page. I LOVE THIS! Now click the Find a Grave ID LABEL. If the person does not have a FaG memorial number already entered, you will get the FaG search results page. If the person does have a FaG memorial number entered, you will get their FaG memorial page. 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 GenealogistsR, used under license by Board certificants who meet competency standards. -- 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] Changing Source List Name
Amen! And while the programmers are fixing things it would be nice if they would fix the scrapbook feature so that it would list document files (for example pdf files) just the same way it lists video and sound files. All that is needed is to use the same logic for the entry in tblBR when PicName = If.jpg (a document file) as is used when PicName = Is.jpg (a sound file) or when PicName = Iv.jpg (a video file). That should take only one additional "Else IF" statement. Howard Cady -Original Message- From: dwquig...@cox.net Sent: Friday, February 12, 2016 8:27 AM To: legacyusergroup@LegacyUsers.com Cc: Brian/Support Subject: Re: [LegacyUG] Changing Source List Name Brian, I only did the table edit in Access on a backup of the fdb file as an experiment to try to find the source of the problem. However, Millenia's constant lack of support for their user's use of Access or other similar tools to accomplish things that Legacy cannot currently do is (in my opinion) very, very shortsighted. It makes us wait for the next slow-developing upgrade that may or may not fix our particular problems with the software. But worse, it stifles the creativity of Legacy users to find ways to improve the functionality of the program or to tailor it to their specific needs and preferences. As an example, the Ltools program that is now free on the Internet, has a very useful to table viewer which I, and I suspect many others, have used to easily and effectively search for missing or mistyped data or inconsistencinies in how we enter our data. As issues are found, they can be fixed directly in Legacy - often by using it's powerful search & replace tool - when it is working :) Sorry for the rant. Just trying to help make the great program, that Legacy is, even better. Cheers, Don Brian/Support <br...@legacyfamilytree.com> wrote: > Modifying internal tables in Legacy is not recommended and you do so at > your own risk. I will not comment on your message other than to say I > hope you made a backup because if you made your file unusable by any > edits you are on your own. > > Brian > Customer Support > Millennia Corporation > br...@legacyfamilytree.com > http://www.LegacyFamilyTree.com > > > > On 11/02/2016 18:46, Don Quigley wrote: > > Brian, > > > > I found this suspicious text in the Contents column of tblSR in the fdb > > database. The highlighted text(0033B - ]should not be there asI > > hadediteditout bySearch & Replace in Legacy. > > > > [Master Source List Name]|0033B -1830 US Census, Hector, NY - Isaac > > Quigley Family|[Jurisdiction State]|New York|[Jurisdiction > > County]|Thompkins|[Census ID]|1830 U.S. census|[Publisher > > City]|Washington, D.C.|[Publisher]|National Archives and Records > > Administration|[Publish Date]|n.d.|[Series]|M19 > > > > > > Editing out the text in the tblSR table and then againin S finally > > made the change permanent - whatever that means ! > > > > Donald Quigley > > > > Escondido, CA > > > > Quigley Doyle Family Tree > > > > -Original Message- > > From: Don Quigley [mailto:dwquig...@cox.net] > > Sent: Thursday, February 11, 2016 2:51 PM > > To: legacyusergroup@LegacyUsers.com > > Subject: RE: [LegacyUG] Changing Source List Name > > > > Brian, > > > > It seems to only be a problem for SourceWriter sources. > > > > Donald Quigley > > > > Escondido, CA > > > > Quigley Doyle Family Tree > > > > -Original Message- > > > > From: Brian/Support [mailto:br...@legacyfamilytree.com] > > > > Sent: Thursday, February 11, 2016 2:11 PM > > > > To:legacyusergroup@LegacyUsers.com<mailto:legacyusergroup@LegacyUsers.com> > > > > Subject: Re: [LegacyUG] Changing Source List Name > > > > This appears to be a bug. You are correct the change seems to take place > > in the Master Source List but when edited the old name still shows. > > > > Our bug reporting system is down right now but I have flagged this > > message and I will submit a report when the system comes back up. > > > > Brian > > > > Customer Support > > > > Millennia Corporation > > > > br...@legacyfamilytree.com<mailto:br...@legacyfamilytree.com> > > > > http://www.LegacyFamilyTree.com > > > > On 11/02/2016 16:37, Don Quigley wrote: > > > >> Has anyone else had the problem of getting Source List Names changed > > > >> by Search & Replace? > > > >> > > > >> After a change in S, the source name appears as having been changed > > > >> in the Master Source List
Re: [LegacyUG] New Legacy Update - We need your help testing
There is still a problem with sharing a “Life Sketch” event by downloading from FamilySearch to Legacy Family Tree version 506. My computer – Windows 8.1 32 bit version with Legacy v8 setup to connect automatically to FamilySearch through My Toolbar. (I do not have the ToolBar problem reported by Jim Terry) I used William Scott FSFT ID LWQM-F3Q for testing as he is the individual I used for reporting “Life Sketch” problems in the past. Version 506 no longer breaks my web connection to FSFT when I already have a LifeSketch event for William Scott (one problem fixed), but when I share the FSFT “LifeSketch” event Legacy only downloads the first 255 characters (half of the first paragraph of the FSFT event) and puts them into the Description field rather than downloading the entire event to the Legacy event Note field (a memo field of essentially unlimited length) Legacy needs to have a test for the number of characters being downloaded so that it can decide to put short descriptions (less than 255 characters into tblER.Description) or long descriptions (more than 255 characters into tblER.Desc – a memo field) Howard Cady From: KenMcGinnis Sent: Tuesday, July 28, 2015 3:32 PM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] New Legacy Update - We need your help testing Hi, We are about ready to release a new General Release build that will support the changes that FamilySearch has made to their API's. We would like any of you who would like to help do some additional testing to please download Legacy using the link below. With this update we really need the Legacy FamilySearch feature to be used and tested. Please try everything you normally do. Share data back and forth with FamilySearch, Merge Duplicates, etc. If you are LDS is everything related to ordinance working for you. If you are not LDS (you won't see LDS ordinance items) but everything else should still work and needs to be tested. All features need to be tried since the API changes affected a bunch of code in Legacy. As always we ask that you please make a backup of your family files before downloading any new update. Here is the link: http://www.LegacyFamilyTree.com/Download/Legacy8Setup506.exe Thanks for your help! Ken McGinnis Millennia Corporation kenmcgin...@legacyfamilytree.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
[LegacyUG] Persistent Error in Sharing Event Data with LDS FamilySearch Database
My OS Windows 8.1, 32 and 64 bit computers, Legacy version 8.0.0.499 setup to connect to LDS FamilySearch with remembered name and password. Some individuals in the LDS FamilySearch database have under “Facts and Events” an entry “Life Sketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. The Life Sketch Event’s description can be quite long and far exceeding 255 characters. When I try to share this type of event by downloading from FamilySearch to Legacy on my computer Legacy does not download anything. A manual work-around is to use Windows ctrl-C to copy the LDS information, generate a Legacy event “LifeSketch” and use Windows ctrl-V to copy the LDS information back into my LifeSketch Notes field (a MEMO field not restricted to 255 characters). There is now a serious problem with my Legacy database. I can no longer connect to the LDS FamilySearch web site with this active individual that has this new “LifeSketch” event because the LDS site considers my information dangerous to their data. This type of error was reported to Legacy months ago and a ticket for repair generated, but the error was not fixed through version 499. I do not know anything about uploading a LifeSketch Event to FamilySearch, but I have my doubts. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
Re: [LegacyUG] Switching fields in an event
Kirsty, Importing data from another program into Legacy and downloading data from FamilySearch into Legacy will have nearly the same problems. The tool I use to see what is going on is Dennis Kowallek’s Zipper Software – Ltools Deluxe version. See web address zippersoftware.com/wp/ltools/what-is-ltools/ for information. Dennis provided strong support through Legacy ver 7.5 and viewing Legacy’s tables still works well. Programming changes to Legacy8’s Event Tables will require learning SQL programming language – not trivial. The work around for you may be to get a new gedcom file from FTM and edit out, with a word processing program, all individuals except those with troublesome events. Then edit the events to have field names that will transfer into Legacy Note fields, and then use legacy’s merge individuals feature. None of this is worth the effort unless you have lots of events with problems. If you only have a small number of troubling events then use Windows split screen feature and display FTM on one side and Legacy on the other. Get the problem event displayed with both programs and use Windows clipboard (ctrl-c/ctrl-v) to put the offending information into Legacy’s Notes, or use FreeClips to do the same thing. Delete anything in Legacy’s Event Description field if you plan to access FamilySearch with an individual using this event. Howard Cady From: Kirsty M. Haining Sent: Wednesday, March 4, 2015 1:47 PM To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Switching fields in an event Hi, Howard — Thanks for taking a stab at answering my question. The issue you faced sounds quite frustrating, and I’m glad you found a solution. Unfortunately, my issue has to do solely with Legacy, and not with its integration with FamilySearch’s tree. I actually had data that came from a FamilyTreeMaker file that was imported into Legacy — the import is already completed and there’s been too much work to go back to the importing step. But that’s how the information ended up in the wrong fields. Once I try to merge this temporary Legacy tree with my main tree (which I haven’t done yet, since I’m trying to clean up and standardize things), I will have a problem with this particular event because the format is so different from my regular Legacy event. There are two possible solutions that I can see — one is to create a new event, and rework all the sentence definitions so that these particular ones use the description field in a different way. The other solution would be to standardize the input of the data by switching the information that is in the Legacy event fields. My preference is for the latter. If there’s a way to do this from within Legacy, that would be terrific. If I need to use Access to switch the field information, I’m open to doing that (although I hope it would be fairly simple to do since I haven’t really used Access to modify my Legacy database before). cheers, Kirsty J Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
Re: [LegacyUG] Switching fields in an event
Kirsty, There is a work around for this error in LegacyFamilyTree, but first I will re-report the error and then give a work around example. My OS Windows 8.1, 32 and 64 bit computers, Legacy version 8.0.0.473 setup to connect to FamilySearch (FSFT) with remembered name and password. Some individuals in FSFT have under “Facts and Events” an entry “Life Sketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. The Life Sketch Event’s description can be quite long and far exceeding 255 characters. When I try to share this type of event by downloading (sharing) from FS to Legacy on my computer Legacy stores the information in Table tblER and tries to store the description in a 255 character field tblER.Description rather than the proper MEMO field tblER.Desc (What a confusing choice of field names!). When the Description field overflows (255 characters) a message is sent to FS that causes it to instantly drop my internet connection and generate an OS Error on my computer. Until I have deleted the offending event I am not allowed to reconnect to FS with that person active. This error was reported to Legacy in September 2014 and a ticket for repair generated, but the error was not fixed thru version 473. I do not know anything about uploading a LifeSketch Event from Legacy to FS, but I have my doubts. THE WORK AROUND – BABY STEPS USING A COPY OF LEGACY’S SAMPLE FILE 1.Create an unattached male - William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. and select him in Legacy’s Individual Information Screen. 2.Connect to FamilySearch by clicking the FamilySearch tool in Legacy – should display 15 possible duplicates 3.Select the Share Tab – should display William Scott’s information - Legacy on the left and FamilySearch info on the right. 4.Find the “LifeSketch” event on the right (FSFT) side and click the share arrow to start the download to your file. This will bring up a screen “Select action to perform” with the right side showing “Legacy” information and the left showing “FamilySearch” with more than a screen full of information. 5.Use the Windows select feature to highlight the FSFT information and ctrl-c to copy the information to Windows clip board. 6.Close the FSFT window, return to the Legacy’s Individual Information Screen, and open the Individual Information Screen to add an event to William Scott’s information. 7.Add a “LifeSketch” event to William Scott. Select the Notes field and use ctrl-v to transfer windows clip board to the Notes field. 8.Enter anything you want into the Date and Place fields, but DO NOT enter anything in the Description field of this event. (Anything in the Description field will prevent connection of this individual for further sharing with FSFT) I do not know which event caused you trouble, but I suspect the same difficulty with any event that has lots of information in the FSFT description field. Howard Cady From: Kirsty M. Haining Sent: Tuesday, March 3, 2015 5:00 AM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Switching fields in an event Hi, everyone — I’m hoping someone has already solved this problem and knows what to do. I have imported data that has information in the description field that I want to be in my event notes field. How can I get the data from these fields to be switched automatically (and, obviously, quickly and efficiently)? Thanks for your help. cheers, Kirsty Haining Seattle, Washington J Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
Re: [LegacyUG] Switching fields in an event
Kirsty, PS I switched the left and right information on the “Shared information” screen for Legacy and FamilySearch. Sorry. Howard Cady From: Kirsty M. Haining Sent: Tuesday, March 3, 2015 5:00 AM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Switching fields in an event Hi, everyone — I’m hoping someone has already solved this problem and knows what to do. I have imported data that has information in the description field that I want to be in my event notes field. How can I get the data from these fields to be switched automatically (and, obviously, quickly and efficiently)? Thanks for your help. cheers, Kirsty Haining Seattle, Washington J Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
Re: [LegacyUG] Event location somehow got changed
Paula, My Legacy Option settings, the use of Geo Mapping and access to FamilySearch make it easy to show that Legacy has several paths where the internal workings of Legacy perform an automatic “combine/combine with” function that ignores the values for Latitude and Longitude. Perhaps the easiest way to see this function in action is to find a new family using the FamilySearch feature of Legacy that has children born in the same location. Use the “this is the same Person as mine” and “Share” option to download to your file one of the individuals and the event using a location of interest. Then go to your Master Location list and the location of interest. Look at the list of individuals using that location. Go back to FamilySearch and download (share) another person and event that uses the same location. Return to your Master Location list and the location of interest. The list of users of the location now includes the newly downloaded individual (an automatic “combine/combine with” for the location). Similarly editing the names for a location from the Master Location list so that saved location names are now identical with those of an already existing location will cause a location merger even though the Latitude and/or Longitude differ. The new Lat/Long are discarded in favor of the older existing ones. If you desire more information, let’s correspond directly – off list. Howard Cady From: Paula Ryburn Sent: Saturday, January 31, 2015 7:11 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Event location somehow got changed Bill, I know about the one where I select the two locations to be combined, but this thread made it sound like there was some internal logic that automatically combined locations. Or maybe I was reading it too late at night? Thx. --Paula From: William Hoff bh...@mchsi.com To: legacyusergroup@LegacyUsers.com Sent: Friday, January 16, 2015 11:53 AM Subject: Re: [LegacyUG] Event location somehow got changed Yes the feature to combine locations is there. I use infrequently but have used, in fact last night Bill On Jan 16, 2015, at 11:01 AM, Paula Ryburn paula.ryb...@sbcglobal.net wrote: I've not heard of this internal 'combine/combine with' feature. Is it truly there? The OP made me think of how many similar locations I have and that sometimes I don't type enough letters to get the correct one to display before I tab on to the next field... and how maybe tabbing accidentally to the field and then doing something (I know we all do something unintentional don't notice it) caused a similar location to display subsequently be saved. I hadn't seen any mention of what the new location is on the records in question. Just a thought. --Paula -- From: Howard Cady howardc...@q.com To: legacyusergroup@LegacyUsers.com Sent: Tuesday, January 6, 2015 12:09 PM Subject: Re: [LegacyUG] Event location somehow got changed I have noticed that when editing locations that my current option selections and version of Legacy V8 (the latest) has an automatic internal “combine/combine with” feature that sometimes creates unexpected results. I have not determined what particular set of matches causes this automatic combine, but I am not using the conventional US 4 place location convention and I do know that mismatched lat/long entries do not prevent combining. This might be the cause for others to have unexpected event changes. Howard Cady Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
Re: [LegacyUG] Event location somehow got changed
I have noticed that when editing locations that my current option selections and version of Legacy V8 (the latest) has an automatic internal “combine/combine with” feature that sometimes creates unexpected results. I have not determined what particular set of matches causes this automatic combine, but I am not using the conventional US 4 place location convention and I do know that mismatched lat/long entries do not prevent combining. This might be the cause for others to have unexpected event changes. Howard Cady From: Gene Wheeler Sent: Tuesday, January 6, 2015 10:05 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Event location somehow got changed Thanks, Ron. Very helpful. Gene On Tue, Jan 6, 2015 at 2:37 AM, ronfergy@tiscali.co.uk wrote: We Do not know! Ron Ferguson Gene Wheeler bridge...@gmail.com wrote: OK, Legacy Support, what's going on here? Gene On Sun, Jan 4, 2015 at 9:29 PM, Jess jrkmorg...@gmail.com wrote: I had this issue as well, and honestly thought I was crazy! I had at least a dozen people with burial location of Bellvieu Cemetery, Benton, Bossier Parish, Louisiana. I know this because I was going from a book and can source every one (it is a family plot). I went to print a list so To make sure I photographed all of them when I went, and it only gave me three people. Jessica Morgan On Jan 4, 2015, at 6:07 PM, Cathy Pinner genea...@gmail.com wrote: O help. I don't think you're going mad. I had this happen the other day but caught it straight away and wasn't sure what I'd done. Just one location changed to a new location I'd just entered. The new location was a birth location. The location that changed was the death and burial location for that person and for everyone using that death location. I know I made a mess of the new entry and edited it a few times as I found out more about the location. I was also having some computer problems and Legacy crashed a couple of times so I put it down to that. I've now restored an earlier image of my computer and all seems well again. Cathy Gene Wheeler wrote: No, no clean-up, no merging, nothing like that. In fact, I've been working on a totally different Legacy file for the past month. Gene O n Sun, Jan 4, 2015 at 10:58 AM, MikeFry emjay...@gmail.com mailto:emjay...@gmail.com wrote: On 2015/01/04 05:43 PM, Gene Wheeler wrote: I'm using the current release of v.8 and have been for months. I just happened to notice that the location for the burial of both of my parents was changed to the same incorrect cemetery. The correct cemetery has been part of their records for years, and now, somehow, they BOTH got changed to the same incorrect cemetery. Any idea what gives? It makes me wonder how many other records got changed without my knowledge. Been doing any spring cleaning of locations? nbsp; -- Regards, Mike Fry (Jhb) Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
[LegacyUG] Error in Share Data between Legacy Family Tree and FamilySearch FamilyTree
My OS Windows 8.1, 32 and 64 bit computers, Legacy (LFT) version 8.0.0.459 setup to integrate with FamilySearch FamilyTree (FSFT) with remembered name and password (Option 1.8 checked). Some individuals in FSFT have under “Facts and Events” an entry “LifeSketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. The LifeSketch Event’s description can be quite long and far exceeding 255 characters. When one matches this individual (This Individual is the “Same Person”) and then attempts to share this LifeSketch event for the above individual and transfer information from FSFT to LFT then the internet link disconnects my computer from FSFT. Attempts to relink LFT and FSFT with this individual highlighted fail when the “Share Data” tab is clicked. Deleting the newly created LifeSketch event recreates normal internet linkage behavior. The Deluxe version of LTools (zippersoftware.com/wp/) is very useful for studying Legacy’s database structure. Legacy stores most Event information in tblER. When sharing a LifeSketch event Legacy tries to store FSFT’s event description into the 255 character field tblER.Description rather than the proper MEMO field tblER.Desc - called Notes in LFT (What a poor choice of field names – no wonder Legacy’s programmers get confused.) and this causes a data field overflow. Such behavior is common with malware and all computers involved should properly drop any internet connections. FSFT also examines Legacy’s tblER before allowing any data transfer from Legacy to FSFT. Apparently FSFT will not accept a data transfer (or internet connection) for an individual with any “LifeSketch” data in the field tblER.Description. Legacy has many event names available and all of them allow both “Descriptions” (tblER.Description) and Notes (tblER.Desc). Programming errors, like that for LifeSketch, is a likely source for unexpected internet behavior when sharing data. This error was reported several months ago and has a position for being fixed, but the error has survived at least two updates. There is a work-around for this error. Use Windows commands ctrl-c and ctrl-v to copy LSFT’s description and paste it into Legacy’s Note field for an added LifeSketch event. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
[LegacyUG] Error in FS Share Data Download of Event Life Sketch
My OS Windows 8.1, 32 and 64 bit computers, Legacy version 8.0.0.454 setup to connect to FamilySearch with remembered name and password. Some individuals in FSFT have under “Facts and Events” an entry “Life Sketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. The Life Sketch Event’s description can be quite long and far exceeding 255 characters. When I try to share this type of event by downloading from FS to Legacy on my computer Legacy stores the information in Table tblER and tries to store the description in a 255 character field tblER.Description rather than the proper MEMO field tblER.Desc (What a poor choice of field names!). When the Description field overflows (255 characters) a message is sent to FS that causes it to instantly drop my internet connection and generate an OS Error on my computer. Until I have deleted the offending event I am not allowed to reconnect to FS with that person active. This error was reported to Legacy about a month ago and a ticket for repair generated, but the error was not fixed for version 454. I do not know anything about uploading a Life Sketch Event to FS, but I have my doubts. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Maintaining Sequence of Twins/Triplets
Mike Fry, I suggest playing with LTools and a COPY of the Sample.fdb file. Generate a twin with your required name order. Then use LTools to change table IR so that the entry for BirthSD (birth sort date) is earlier for the first born by a day, but leave the entry for BirthD to be identical for both twins. See if this fixes the name order for the twins in reports and Legacy tables to reverse the name order as you want. Finally see if Legacy’s file check/repair features complain or reset BirthSD. It is not trivial to learn to use LTools, but it provides a way to deal with situations such as the one you describe. From: Ron Taylor Sent: Wednesday, August 13, 2014 8:53 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Maintaining Sequence of Twins/Triplets If all the children connected to a marriage have birthdates, then the children sort could easily be done by birthdate, sibling order, given name. If the children have been manually ordered, the children should stay in the set order. If the order has not been set, then child sort would be like it is in the current version (as if order = 0 for all siblings). This SQL illustrates this sort for children of a specific MRIN where all children have a birthdate. The WHERE clause specifies the MRIN of the parents to use. SELECT tblCR.IDIR, tblIR.BirthSD, tblCR.Order, tblCS.ChildStatus, tblIR.GivenName, tblIR.Surname, tblCR.IDMR, tblMR.HusbGivenName, tblMR.HusbMarrSurname, tblMR.WifeGivenName, tblMR.WifeSurname FROM ((tblCR INNER JOIN tblIR ON tblCR.IDIR = tblIR.IDIR) INNER JOIN tblMR ON tblCR.IDMR = tblMR.IDMR) INNER JOIN tblCS ON tblCR.IDCS = tblCS.IDCS WHERE (((tblCR.IDMR)=1)) ORDER BY tblIR.BirthSD, tblCR.Order, tblIR.GivenName; If any child does not have a birthdate in the database, then the children should be sorted by order, given name or the children with birthdates could be displayed in date order followed by the children without birthdates. They would need to be manually ordered or the birthdates could be set to Abt dates so that a later sort will order them. When the sort children by birthdate, order, given name or just by order, given name is complete, the order numbers can be re-assigned. The same logic would apply in the new tool for sorting all children in the database or a single family in Children Settings. On Wednesday, August 13, 2014 7:25 PM, Cathy Pinner genea...@gmail.com wrote: Hi Sherry, I suspect that you're not a twin nor a sister to a twin. I think your usually relates to people who are not closely connected to twins. I have older twin sisters born only half an hour apart. I've always known who the eldest one is - and the order is not the alpha order. There are also a number of sets of twins amongst my cousins - and again I know which one is the eldest in most cases. Fortunately I don't global sort very often - probably never again as I don't import files these days. I don't know a way to stop them reverting to alpha order on a global sort. Cathy Sherry/Support wrote: Is it that critical that the first-born twin be listed first? Usually people only consider the date, not the time. You could make an Event showing which twin was born first and include the time of birth or put it in their Birth Notes. It looks like the twins sort in alpha order as a sub-sort. I have several sets in my line and when I sort, they're always i n that order. We do have a suggestion listed to be able to include time with the date but I don't know if this is something the programmers will be able to implement or not. Honestly, this is such a rare request You're the second person on the suggestion list. Sincerely, Sherry Technical Support Legacy Family Tree On Wed, Aug 13, 2014 at 8:18 AM, MikeFry ​​ emjay...@gmail.com mailto:emjay...@gmail.com wrote: On 13 Aug 2014 15:30, Sherry/Support wrote: You can manually sort the children in the Edit Children window (right click on a child and select Children's Settings. Yes! But if the file ever gets sorted again, the sequence gets messed up. -- Regards, Mike Fry (Jhb) --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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:
Re: [LegacyUG] Legacy Family Tree - Virtual User's Group Meeting this Friday, July 11 (Dates, Searching and Tagging)
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 From: Geoff Rasmussen Sent: Thursday, July 10, 2014 9:58 AM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy Family Tree - Virtual User's Group Meeting this Friday, July 11 (Dates, Searching and Tagging) Join us this Friday, July 11, 2014 for our next Legacy Family Tree Virtual User's Group Meeting. Learn tips, tricks, and best practices related to using Legacy. Beginning through advanced topics will be discussed - specifically dates, searching, and tagging. We'll also have time for questions and answers. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
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 OptionsCustomizeDates, nor is it mentioned as a prefix under HelpIndexDates ApproximatedPrefixes, nor is it mentioned under HelpIndexDates 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 Sent: Thursday, July 10, 2014 12:50 PM To: legacyusergroup@LegacyUsers.com 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 1familytree@gmail.com 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 in a marriage date as 18 yrs after the youngest spouse. I use bef in a marriage date when I know the birth year of a child I use aft in a birth date when I know the marriage year of the parents I use bef in a death date when I see their spouse is widowed on a census and I use abt 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 howardc...@q.com 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Research guidance - Goal with no suggestions
Michelle in Support I believe you are missing Kathy Thompson's point. I think she is asking LegacyFamilyTree's Research Guidance to have your logic built in. That is for the program to be intelligent enough to determine that there is a missing death date for a person and then use the generic rules you describe to make suggestions as to where to look for the missing information. She wants to avoid entering guessed data into her known genealogy file. If the person is born in England, married in England, and has English descendants then one would expect English vital records to be listed ahead of French, German, or American sources, if these latter sources are mentioned at all in the Research Guidance. Howard Cady - Original Message - From: Michele/Support To: LegacyUserGroup@LegacyUsers.com Sent: Thursday, December 26, 2013 8:10 AM Subject: RE: [LegacyUG] Research guidance - Goal with no suggestions Kathy, If I have nothing but a marriage record I assume the groom was abt 21 and the bride was about 18. If I have nothing but the date of birth of the children, I find the oldest know child and calculate the marriage date 1 year before that and then their ages using the 21/18 rule. If you have a marriage or a baptism, you have at least one location on their timeline for the Research Guidance to work with. When I put in a test person with one date and England as a location I got the specific databases you listed. Michele Technical Support mich...@legacyfamilytree.com http://www.LegacyFamilyTree.com From: Kathy Thompson [mailto:kmthoms...@gmail.com] Sent: Wednesday, December 25, 2013 10:04 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Research guidance - Goal with no suggestions Not the point though Michelle - I personally have some ideas, but Legacy is giving me no suggestions on where to look I do have a number of Alt. Death events for people who I am uncertain of when they died - even those don't help Legacy to give me hints like the regular normal ones ofCemeteries, World-wide or England Probate Records or England/Wales Parish Register - Burials etc It doesnt even have these as suggested soources for this person No, I didn't find the names from Obituaries, if I had, I'd have a death date or at least year for them I have the names from the baptisms of their children or their own marriage document, or from census records. No I can't always use the census records because some of these people died after the last available census for the area (ie 1911 in England) Yes, some did die between census records, and for those I don't need the hints because I have a very defined time frame. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Tagging Marriages
Laura, if you are slightly able to deal with databases and their structures, then I would suggest considering the Legacy add-on LTOOLS for major clean-up, and special tagging (marriages can have up to three tags). Dennis Kowallek, the LTOOLS programmer, has helped others with similar problems. It may be possible to fix all FTM to Legacy conversions that have been messed up by the standard export-import process for all of your 54,000 individuals and 17,000 marriages by direct manipulation of a copy of the Legacy database because you are dealing with only one version of FTM and only one version of Legacy. NEVER work on your original family file with LTOOLS - only use a copy of your original file. Howard Cady - Original Message - From: Laura Johnson rngad...@madisontelco.com To: LegacyUserGroup@LegacyUsers.com Sent: Saturday, October 26, 2013 7:52 AM Subject: Re: [LegacyUG] Tagging Marriages This would have been a great idea EXCEPT that once you get the list, you are NOT getting the marriages to tag. You still get a list of individuals to tag. I already have tagged all individuals in the database and have been working my way through cleaning those up. There are 54,833 individuals and 17090 marriages. The results of the trial run for this created a list of 52,601. But if you look at the list, I would be re-tagging several thousand people that I had already cleared the tag on as my search list for the tag I was doing shows that I still have 49,654 still to go from my original tagging. First, let me tell you what I have been doing. I have been entering all of the births, marriages and deaths from 1820 through 1910 from the microfilmed records from a town in Sicily. I also have an online database for this town as well that is fully searchable. I had been a loyal user of FTM from the early 1990's and had beta tested for them for years. After beta testing their 2008 and 2009 versions, it was evident that Ver 16 was going to be the last version I would use due to the changes they had made to the program. The newer versions cannot handle my file and scramble the details on sources when they are imported via gedcom from Ver 16 to FTM 2008, etc. I switched to Legacy on the advise of a friend who had been using it for years. It was far superior to what FTM had in any version that I had used. So I bought the deluxe version and have been using it ever since. But in bringing my files over to Legacy, I noticed that I needed to do cleanup on the way I had been doing things before I started using Legacy and even after I first started using Legacy because I found other options or ways of doing things that were far superior in Legacy and I need to cleanup and redo things that were not done that way in the past. About a year ago, I tagged all individuals in the database with Tag #5. The description for this tag is: FTM Cleanup Needed. I also have tag 2 and tag 3. These tags designate my paternal great-grandfather's family (#2) and my maternal great-grandmother's family (#3). This way I can easily see if a person is included in my ancestral lines or is just someone from the town. I have been working my way through the tag #5 as I enter more data in the file and cleaning them up as I go. But it would be easier if I could see that the marriage tag was cleared because then I would know that I had already changed or fixed any problems with the children and descendants of that line. I wouldn't need to choose each of the children one by one to confirm whether they were done or not. My thoughts were originally to use the marriage list to tag so that I could work through all of the marriage list. I would select the first marriage on the search list, correct both the wife and husband and any children they had and remove the tag numbers for both the marriages and the individuals as I went for that marriage. Then once I had worked through all of the marriages, I could then do a final search to find any unlinked individuals Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
[LegacyUG] Obsolete FamilySearch IDs
I have noticed that the FamilySearch IDs for some of the individuals in my Legacy file are now obsolete as indicated by a red chain linkage symbol when I do a new FamilySearch that shows that individual. I assume this is caused by someone changing the current LDS FamilySearch database from the IDs used by the obsolete newFamilySearch. Is there a global search technique that will produce a list of all such obsolete individual FamilySearch IDs in my Legacy file? If not, is it a worthwhile suggestion for a future feature for Legacy and its FamilySearch features? I expect this to be a continuing item as the LDS FamilySearch data base and its preferred IDs continue to be updated/changed in the future. Howard Cady Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Obsolete FamilySearch IDs
Paul, The Red Chain link Icon appears on the split screen view-Legacy My Legacy Person side that is generated when the Open FamilySearch Tree toolbar button is clicked for an individual highlighted in Legacy's Family View and the Share Data tab is selected. I have not done a complete check to determine if old IDs are always available somewhere on some LDS site, but sometimes the old ID is still in the list of Possible Duplicates and sometimes it can be found by replacing a preferred FamilySearch ID with the old FamilySearch ID in Legacy's Family View and then repeating FamilySearch. When Legacy (version 219? or earlier) was using the newFamilySearch database to transfer of data to my Legacy file, then it also generated a source reference for that data. The new build of Legacy (270) no longer generates a source reference for FamilySearch data and I have been unable to find a way to do so automatically. I agree with you that the reason for ID changes has its roots in the merging of individuals in the LDS database. Howard Original Message - From: Paul Gray graypa...@outlook.com To: LegacyUserGroup@LegacyUsers.com Sent: Saturday, September 21, 2013 5:21 PM Subject: RE: [LegacyUG] Obsolete FamilySearch IDs Howard, Could you give a bit more detail as to where you are seeing this 'red chain'? I think it's most likely that the individual has been merged into another on Family Tree by some other user. But, just to see if that's the case, have you tried to go into family Tree directly (on the LDS site) and try to bring up the 'missing' individual? Paul Gray -Original Message- From: Howard Cady [mailto:howardc...@q.com] Sent: September-21-13 4:11 PM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] Obsolete FamilySearch IDs I have noticed that the FamilySearch IDs for some of the individuals in my Legacy file are now obsolete as indicated by a red chain linkage symbol when I do a new FamilySearch that shows that individual. I assume this is caused by someone changing the current LDS FamilySearch database from the IDs used by the obsolete newFamilySearch. Is there a global search technique that will produce a list of all such obsolete individual FamilySearch IDs in my Legacy file? If not, is it a worthwhile suggestion for a future feature for Legacy and its FamilySearch features? I expect this to be a continuing item as the LDS FamilySearch data base and its preferred IDs continue to be updated/changed in the future. Howard Cady Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] What happens if linked person deleted in Family Search
Paul, I can confirm that you are addressing a real concern. I have had the FamilyTree search function of LegacyFamilyTree v219 change some of my FamilySearch IDs from say P21X-J6L to say XYZ2-4LQ without any request for permission or any notification by LegacyFamilyTree when I was using the LDS FamilyTree Search function. Forcing a new search using the old P21X-J6L identification number does not always find the correct individual in the LDS database. I also suspect that merging individuals within the LDS file is the source of this behavior. Because I do not wish to compound problems in the LDS FamilyTree database, I have avoided doing anything that would try to fix errors or merge individuals in the LDS FamilyTree database at the present time. It is hoped that improved programming and detailed sourcing of information will fix things for us in the future. - Original Message - From: Paul Gray To: LegacyUserGroup@LegacyUsers.com Sent: Wednesday, August 28, 2013 3:49 PM Subject: RE: [LegacyUG] What happens if linked person deleted in Family Search I think we are talking about different links. What I am referring to is the link that is created when in LFS I click on the button ‘this person is the same as mine’. That tells my Legacy file (and only my Legacy file) that as far as I am concerned, RIN 1234 in my file is the same person as Family Tree person id P21X-J6L, or whatever. (that person id is made up, although it might really exist in the file). Yes, I do carefully evaluate all potential duplicates of P21X-J6L, and merge as appropriate. I usually end up keeping data and events from multiple person id’s as there is usually valid data (verified by outside historical records) in those records. i.e. one might have two of the five children, and another person id the other three children. Anyway, I do my best and at the end to the best of my ability I have person P21X-J6L that to the best of my knowledge is the only valid record for this person. Somebody then comes along and disagrees with me, and merges P21X-J6L into someone else. My link in my Legacy file from RIN 1234 now points to a deleted (merged) person id in Family Tree. Similarly, it’s possible that some other Legacy (or Roots Magic or whatever user) currently has a pointer in their file to a record I deleted/merged into P21X-J6L. I’m not questioning whether this should or shouldn’t happen, as there really is no alternative with a shared database. I’m just asking if LFS detects this kind of thing, or whether we just find out whenever we next try to access the record in LFS. Paul From: Eliz Hanebury [mailto:elizhg...@gmail.com] Sent: August-28-13 2:06 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] What happens if linked person deleted in Family Search Legacy sure does warn you about possible duplicates after the merge, during the merge you must check for links and events, if you do you will catch any link you want or don't want. Eliz Not Today and Not without a Fight (Anon) For all that has been, thanks. For all that will be, yes. (Dag Hammarskjold) On Wed, Aug 28, 2013 at 4:02 PM, Paul Gray graypa...@outlook.com wrote: I've been using Legacy Family Search for a short while now, and have linked 25-30 ancestors to my Legacy file. In doing the linking, in some cases I have also merged duplicates in Family Tree. When I merge, I effectively delete one or more people. It's possible that one of those deleted people is already linked to individual in another Legacy file (or other compatible program) file elsewhere in the world. And, of course it's possible that some other user will merge one of 'my people' and that link will now point to a nonexistent Family Tree person id. Does Legacy warn me about this, or will I just find out six months down the road when I use LFS to look at the record in Family Tree? Thanks, Paul Gray Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy
Re: SV: [LegacyUG] Surprise during today's webinar
Marie, I'm with you!! (Fields for birth, marr, death, separate fields for dates (month, Day, Year and places, Location, city, county, state, country) I am so surprised that these fields haven't already been added !! I really Hope they are in the next big upgrade! On Fri, Jun 7, 2013 at 5:12 PM, mvmc...@aol.com wrote: I'm with Brian. I'm still waiting for the ability to have separate field for day, month, year of birth, death and marriage as well as fields for city, county and state. I used to have them way back in the Roots/Visual Roots times. So I do a work around. Legacy keeps track of my data. All The fields you are requesting are already present in the Legacy database. Location currently has 9 fields, not just the four being mentioned. As for dates, an example is the birth date word which is 18 characters long . the first character specifies the prefix such as Est, Abt, Bef, Between, etc. The second character is probably a control for A.D. /B.C. (I don't have any B.C. dates) followed by ddmm as 8 characters followed by another set of ddmm that is used when a second date specifies a range (ie. Between). Ltools is a useful program for inspecting the database structure and is easier to use than the free Libre Base. Legacy translates this date word back into the readable format you request. Howard Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Persons with only assumed/acquired surnames
I handle things similarly, but over the years have found a need for unique identifiers for unknown persons and a guesstimate for their year of birth. This is the system I use - for what it is worth. As names become known their bbb identifier can be recycled and so far I have not needed more than the 18278 unknown individuals available using this three letter identification system. CONVENTIONS FOR UNKNOWN NAME ENTRY Unknown First Name: enter ?am for a male, ?af for a female, ?au sex unknown. Unknown Last Name: enter ??abbb where a in both first and last names is a single capital letter code giving the approximate 33 year span (a generation) for the estimated year of birth. The century and codes follow: YearsCodes YearsCodes 1200-1299 A,B,C 1600-1699 M,N,O 1300-1399 D,E,F 1700-1799 P,Q,R 1400-1499 G,H,I 1800-1899 S,T,U 1500-1599 J,K,L 1900-1999 V,W,X 2000-2067 Y,Z bbb is an entry sequence code that starts with a through z, then aa through az, ba to bz etc. An example using a female with unknown first name, born about 1750, who is the 54th person with unknown last name would be entered as ?Qf ??Qbc. Formula for arriving at date code for b.(birth) to use with unknown name is: 1. Use b. if known 2. Use b. of spouse, or spouse of spouse (other wife etc.) 3. Use first m.-25 4. Use bp+33 where bp=b. of parent 5. For bp use bc-33 where bc=b. of child in next generation For bc use bp+33 where bp=b. of parent in previous generation 6. Use d.-65 8. Use dp-32 where dp=d. of parent 9. Use mc-53 where mc=m. of child 10. Use 33 years per generation from any known date. Howard Cady - Original Message - From: Jerry jerrysemailgro...@gmail.com To: LegacyUserGroup@LegacyUsers.com Sent: Saturday, March 17, 2012 1:16 PM Subject: Re: [LegacyUG] Persons with only assumed/acquired surnames Thanks for those samples, David. What I could not quite figure out is how you are using the FIRST NAME and LAST NAME fields, from your examples, but it gives me the idea of what you are doing. Thanks, --Jerry On 03/17/2012 02:29 PM, David C Abernathy wrote: Jerry, Here are a few samples. They are from my main database from a different program, But, I do the same thing in all of the programs I run. Yes, the person index has all of these people at the top of the index, as the ( comes before any of the letters. As you can see there can be many different combinations, but they work for me. I use a GEDCOM to go from my main database to Legacy and other programs that I have installed. ? Bowlen (Husband of Isabell Abernathy) ? ? (Wife of Charles Madison) Jeanette ? (Wife of ? Moore Karen ? (Wife of Charles Dunivan) Dagmar ? (Mother of Ludwig Alfred Larsen) Doris ? (Wife of Albert Abernathy) Thanks, David C Abernathy Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
Re: [LegacyUG] Pointers and Intellimerging
bk and Dennis This sounds like an important enough problem that the Users Group and Legacy Support should know the required fix. Please keep us informed. It seems like the obvious File Maintenance Check/Repair solution should have been a fix and we need to know why it failed. hc - Original Message - From: britton...@comcast.net To: LegacyUserGroup@LegacyUsers.com Sent: Thursday, February 24, 2011 7:37 PM Subject: [LegacyUG] Pointers and Intellimerging I have another Intellimerge to do, and one file has at least one pointer problem. It manifests as a family file traversible only in one direction, i.e. in this instance traversal upstream deadheads unexpectedly, while traversal downstream from the eldest ancestor completes correctly. From prior experience, I expect that this probably means duplication of a main line individual with the upstream pointer unlinked but the downstream pointer of the parent properly linked. (Before someone suggests it, file repair doesn't seem to fix this.) Four questions: a) Is there any convenient way of locating asymmetrical and/or missing file links in corrupt Legacy files? b) If I perform an Intellimerge with the bad file to the right, will the corrupt structure be discarded on completion, or propagate to the left? c) What causes this kind of file defect and/or data duplication? d) This problem seems to propagate through a gedcom export/import cycle, but could it be fixed easily when the file is in gedcom form? Thanks in advance for any thoughts, kb Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Citation Search / Report
I think this is what you want. Open Legacy and select your file. Then ViewMaster ListsSourceShow Only and check only Source Writer boxOptionsPrint etc. I have tried to reply in text only mode. Will find out soon. - Original Message - From: Frank J. Wesslowski To: LegacyUserGroup@LegacyUsers.com Sent: Friday, December 24, 2010 3:53 AM Subject: [LegacyUG] Source Citation Search / Report Hi, I am new to this board and hope this is the correct place to ask for advice on the Legacy Family Tree. In the Deluxe Edition of Legacy 7.4 I am trying to find a way to list all source citations (created using the SourceWriter method) which do NOT have ‘Include this Citation on Reports’ checked. Is there a way to do this? The reason for this is that I would like to review these records to decide whether I might want to include the source in future reports. Alternatively, is there a way to find this from one of the source citation reports? Please let me know if I need to provide any further information. any help would be greatly appreciated, Kind regards, Frank Wesslowski Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
[LegacyUG] Booby Trap in Editing Locations
I have been moving a fair sized (over 2 individuals) genealogical file from Family Tree Maker to Master Genealogist to Legacy via GEDCOMs. One of the first steps to getting the file in order is to clean-up the Master Location List. I want to locate places by latitude and longitude and its proper historic name. I have been working primarily from Legacy's Master Location List with Show People, Show Map, Sort the Location List, and option - Jump with Edit Sorting checked. Sort is Right to Left (position 1 is on the right), and Legacy's Geo-location database is installed and the Geo text files modified to add Co. to USA county names and change USA as a country name to United States. I have used the Edit button and Combine/Combine-With buttons extensively to get final place names, locations, and lists of individuals using each historic location to be correct. In this process I have discovered that there is a Legacy FEATURE (as per Legacy Support from a bug report) that has caused me real grief. The Edit button on The Master Location List brings up an Edit Location screen that has editable boxes for: Preposition, (Long) Location (9 fields separated by commas), Short Location (9 fields separated by commas), Notes, Latitude, Longitude, and a box for verified (a total of 23 fields for information). There are buttons for Save, Cancel, Help, and Show Geo Location List. When one enters data in these boxes and selects Save then a warning box with the message This change will affect all records using THIS location . is superimposed on the Master Location List screen that shows a list of People using THIS location. If Yes is selected and there is another location in the Master Location List with the identical LONG Location 9 fields then the newly entered location information is deleted and the individuals associated with this new information are added to the list of individuals using the other existing, but perhaps different, location. This means that Legacy only checks 9 of 23 location fields before performing an automatic Combine/Combine-With sequence. NOT NECESSARILY A DESIRED MERGER. Other than being very careful, is there a way to edit the Master Location List that does not use the Edit button? Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
