Page 2 of 2

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 18:07
by gapperly
It seems to be a problem with the gedcom. It ran against an different FH project with no error. I have no idea what to look for.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 18:26
by Mark1834
Sorry about that Gerald. Does the same RM file work correctly with the old FHUG plugin?

The error is in the code that reads the RM parent-child relationships, suggesting there is something there it doesn't like.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 18:56
by Mark1834
OK, thanks. I'll experiment on a test project to see if I can duplicate the error.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 18:59
by jelv
Would the RM version be relevant?

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 19:26
by gapperly
Yes, the old plugin gave the same error. The last time I used it successfully was in September. I have since deleted the old plugin.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 19:28
by gapperly
The RootsMagic version is 7.7.0.0

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 20:00
by gapperly
I think the problem is the RM file not the FH file. I have 2 projects, FHA and FHB, and two corresponding RM files, RMA and RMB. I can run "Compare" of either FH file against RMB with no error. Running either FH file against RMA gives the same error.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 20:07
by jelv
To absolutely confirm you could create a new FH project with only a single individual that won't match anyone in the RM database with minimal facts and try the problem RM database against that.

Have you tried running any of the RM repair routines?

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 21:02
by Mark1834
The error seems to suggest that RM has somebody defined as a child in a family who is not listed as an individual, which seems odd.

I’ve sent Gerald a private message with a couple of suggestions for diagnosing.

Re: FH-RM-Ancestry Sync error

Posted: 20 Feb 2023 21:11
by gapperly
Resolved. I ran the four items available in RM under File>Database tools... I don't know which one did the trick, or what the issue was ( I probably should have run them one at a time, oh well). Thanks for your support.