My goodness that is a nightmare with everyone picking different people. I will be "Very" interested in what others have to say.
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 5:49 PM, Paul Gray <graypa...@outlook.com> wrote: > 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 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 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 on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp