I hadn’t thought to use Search, but I found the cause - wrong person married, in fact her brother. Although similar name to her actual husband, I am amazed that I made such a mistake. I need to be more alert!
Ian T From: Ian Macaulay<mailto:macau...@icmac.ca> Sent: Sunday, 18 June 2017 2:44 PM To: Legacy User Group<mailto:legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Descendant report problem (fixed, cause discovered) Ian T. You should check for duplicate parents. Under misc in search there is a check box. If this is a silly suggestion please just ignore it. It is however what caused me to get a similar error. On Sat, Jun 17, 2017 at 10:50 PM, Ian Thomas <il.tho...@outlook.com<mailto:il.tho...@outlook.com>> wrote: I discovered the cause – I had sister and brother married. Fixed that. Problem solved. It probably needs Legacy program to suggest to user what the cause might be – and, for the check/repair to generate an error for this condition and suggest its cause. Though of course the situation is not unheard of. If it is true, what should Legacy FT do? In this case for my data – it was untrue. Ian Thomas Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com<mailto:legacyusergroup-boun...@legacyusers.com>] On Behalf Of Ian Thomas Sent: Sunday, 18 June 2017 11:57 AM To: Legacy User Group <legacyusergroup@legacyusers.com<mailto:legacyusergroup@legacyusers.com>> Subject: [LegacyUG] Descendant report problem I have a weird error message when running a Descendant report at 5 generations – OK at 4 generations. Legacy v9 flags a marriage and gives me MRIN and the couple’s names. The message is that it has processed the marriage 3 times, and there is danger of an endless loop. I backed up, ran Check/Repair (see my previous posting to this list, about same-sex relationsship reporting as a possible problem), and after re-running the check/repair I have tried the same Descendant report – with the same result. The error message allows 2 more loops before stopping – I chose that, and printed the page on which that error occurs (very grateful for that error-checking coded into Legacy, which allows some clarification). The printed report shows the wife twice (her RIN 710) at gen 5, so I checked her parents children: she is the last born, no ‘duplicate’ (and I would not expect the RIN number to be duplicated). Her DOB is too soon after birth of previous child (but that’s the data I have, and I have seen that problem before with no affect on Descendant report). All I can think of doing is to unlink her from the marriage and her parents, and relink. Any other suggestions to try? Ian Thomas Albert Park, Victoria 3206 Australia -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com<mailto: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/ -- ICMac Sales: Hobby consultant (1986r.) Office hours: 10:00 Am - 5:00 PM most days Macaulay Genealogy Family Matters Ian Macaulay of 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/
