>From the Legacy Help file for Endless Loop. You can get right to it by clicking on the "Help" button in the message window that pops up.
"As the current report was being built, the same person was found in more than one place. This can legitimately happen when relatives of any kind marry each other...cousins for example. It can also happen if an individual is linked in erroneously...such as a grandfather being linked in as a son. This causes an endless relationship loop that must be corrected. "Legacy only warns of a duplicate after it has encountered the same individual three times. When a warning is given, you can either: "1. Set the number of additional encounters by clicking the up and down arrows to the right of the text box and then continue on by clicking the Continue Processing... button. "2. Note the individual or couple listed at the top of the warning box and then click Cancel the Report to stop building the report. You should then research and fix the relationship loop problem. "You can also generate this report with the option to exclude duplicate lines. To do this, click the Report Options button on the menu and select the Don't Repeat Duplicate Lines option on the Format tab." Sincerely, Sherry Technical Support Legacy Family Tree On Sun, Mar 3, 2013 at 7:10 AM, Brian Lehman <blr...@optonline.net> wrote: > Hello all, > I am having a problem I've never encountered before. I just entered a > large generational family. > While going through the Descendant tab, I get a pop up, that says: > "This marriage has now been processed 6 times. You could be in an > endless loop. Note this MRIN # and check it later. and Warn after 5 > encounters". I continue and get the same message, this happens on MRIN > 746 and 336. Two messages then continues as normal. > On MRIN 746, is a married couple, Sam and Hannah, they had 8 > children, one of which is Elmer, > and Elmer is the MRIN 336. He has no wife but a son. > I've checked all relationships, marriages, children etc for these 2 > MRINs, everything looks good, > ran all "File Maintenance", and still the problem continues. > I now have no Idea where to check this or how to fix this. I would > appreciate any advice on dealing with an "Endless Loop". > Than You, > Brian Lehman > New York 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
