Hi: I just (few minutes ago) sent an email with a screenshot of what I just discovered AGAIN in my database ---- triplicated couples as parents and grandparents of EACH OTHER. This is the same thing I came across a few weeks ago and Bruce thought I had probably accessed a wrong database (could be possible) and assured me that 'backup/restore' constantly could NOT have created the problem. I ONLY found this one, same as the previous one, as I was randomly doing some clean-up!!!! The furthest back backup and/or database I appear to have is February 2014 .. the triplication of what I found two weeks (or so) ago is NOT in that database. The triplication of what I found just now (screenshot TURGEON) IS IN THAT DATABASE These folks all only have one ID number, not duplicates. I did finally find the person from whom it begins to triplicate (or worse) back. I have NO IDEA how to search for more of these critters that may exist throughout my database to fix/untangle them .. I have NO IDEA what is making it happen .. I will have lost WAY TOO MUCH DATA that I can't recover if I kill this database (backup) .. HELP!

Hi Pat, I don't think I have ever had triplicates, but I have occasionally over the years managed to get the generations mixed up, I think most often, by accidently making a person a child or a parent of the other. This tends to happen in merging families I have duplicated in my database in slightly different forms. First of all I unlink the offending generations. Then I do what is below if that does not seem to remedy the problems. When I do find a mess where people are children are parents and grandparents of each other (I am sure of my own creation), I write down the record numbers of the offending person or two, then carefully UNLINK ALL OF THE RELATIONSHIPS except perhaps the marriage. On paper I then remind myself of where I need to relink. After unlinking I REINDEX the database (under the file menu and database tools). It never hurts do to a series of backups - naming them something unique instead of writing them over each other. I have even gone so far in the past (maybe one one or two times in 10 years) to remove the offending person from the database, reindex, restart RM and the computer, and put the person back in. I don't ever remember where I could not solve the problem. As a last resort, you might make a gedcom after removing the offensive party, reimport that gedcom to a new database, then add the person or persons causing the problem. I think I have done that once in 15+ years. Over the years I have learned to use estimated dates frequently because it helps prevent mixing up people with the same names in different generations. Just recently I had, say a John Welton with wife Rebecca, for two generations and no dates. That for me is a disaster waiting to happen. Good luck, I'm sure you will get it all worked out eventually without losing data. Let us know what works for you. Margaret Scheffler -----Original Message----- From: Pat McGrath via Subject: [RMagic] My triplicated pedigree chart !!!! Hi: I just (few minutes ago) sent an email with a screenshot of what I just discovered AGAIN in my database ---- triplicated couples as parents and grandparents of EACH OTHER. This is the same thing I came across a few weeks ago and Bruce thought I had probably accessed a wrong database (could be possible) and assured me that 'backup/restore' constantly could NOT have created the problem. I ONLY found this one, same as the previous one, as I was randomly doing some clean-up!!!! The furthest back backup and/or database I appear to have is February 2014 .. the triplication of what I found two weeks (or so) ago is NOT in that database. The triplication of what I found just now (screenshot TURGEON) IS IN THAT DATABASE These folks all only have one ID number, not duplicates. I did finally find the person from whom it begins to triplicate (or worse) back. I have NO IDEA how to search for more of these critters that may exist throughout my database to fix/untangle them .. I have NO IDEA what is making it happen .. I will have lost WAY TOO MUCH DATA that I can't recover if I kill this database (backup) ..

I spoke with Tech Support this morning (heads up that I'd sent them an email) and that is exactly what they did ... unlink the first offending connection and all disappeared. That's pretty much what I had done when I found one of these a few weeks ago .... but my bigger questions were 1) what am I doing that created these (making the assumption that it was operator error and 2) is there any kind of a 'tool' in RM to help find loops like these. None of the people were duplicates with different ID numbers (checked that) ! Turns out THIS loop existed back in February 2014 and was not detected until I did a minor tweak on something today that put them in the visual pedigree screen!!!! Otherwise guess you never find these things and when I'm gone my kids will think I did a terrible job and not trust anything in the database! Fixed 'for now' ------ but MAY I REQUEST SUCH A Problem Identifier be added to tools or problem alerts PLEASE !!!! Do I have to submit that formally? Pat -----Original Message----- From: MScheffler [mailto:[email protected]] Sent: Monday, March 09, 2015 3:09 PM To: Pat McGrath; [email protected] Subject: Re: [RMagic] My triplicated pedigree chart !!!! Hi Pat, I don't think I have ever had triplicates, but I have occasionally over the years managed to get the generations mixed up, I think most often, by accidently making a person a child or a parent of the other. This tends to happen in merging families I have duplicated in my database in slightly different forms. First of all I unlink the offending generations. Then I do what is below if that does not seem to remedy the problems. When I do find a mess where people are children are parents and grandparents of each other (I am sure of my own creation), I write down the record numbers of the offending person or two, then carefully UNLINK ALL OF THE RELATIONSHIPS except perhaps the marriage. On paper I then remind myself of where I need to relink. After unlinking I REINDEX the database (under the file menu and database tools). It never hurts do to a series of backups - naming them something unique instead of writing them over each other. I have even gone so far in the past (maybe one one or two times in 10 years) to remove the offending person from the database, reindex, restart RM and the computer, and put the person back in. I don't ever remember where I could not solve the problem. As a last resort, you might make a gedcom after removing the offensive party, reimport that gedcom to a new database, then add the person or persons causing the problem. I think I have done that once in 15+ years. Over the years I have learned to use estimated dates frequently because it helps prevent mixing up people with the same names in different generations. Just recently I had, say a John Welton with wife Rebecca, for two generations and no dates. That for me is a disaster waiting to happen. Good luck, I'm sure you will get it all worked out eventually without losing data. Let us know what works for you. Margaret Scheffler -----Original Message----- From: Pat McGrath via Subject: [RMagic] My triplicated pedigree chart !!!! Hi: I just (few minutes ago) sent an email with a screenshot of what I just discovered AGAIN in my database ---- triplicated couples as parents and grandparents of EACH OTHER. This is the same thing I came across a few weeks ago and Bruce thought I had probably accessed a wrong database (could be possible) and assured me that 'backup/restore' constantly could NOT have created the problem. I ONLY found this one, same as the previous one, as I was randomly doing some clean-up!!!! The furthest back backup and/or database I appear to have is February 2014 .. the triplication of what I found two weeks (or so) ago is NOT in that database. The triplication of what I found just now (screenshot TURGEON) IS IN THAT DATABASE These folks all only have one ID number, not duplicates. I did finally find the person from whom it begins to triplicate (or worse) back. I have NO IDEA how to search for more of these critters that may exist throughout my database to fix/untangle them .. I have NO IDEA what is making it happen .. I will have lost WAY TOO MUCH DATA that I can't recover if I kill this database (backup) ..