Kevin -
Deleting Denise WifeTwo Doe from the program fixes the Descendant Chart problem. So the problem is caused by second marriages in previous generations.
Ray
Kevin -
My second attempt to send you my RM file also failed. If there’s any way to send it to you directly, let me know. Otherwise, Diana of your support team should have access to it.
Ray
Kevin -
I sent you my RM file (“Test.rmtree”), but I received an error message saying that my attachement was rejected. I’m trying again, sending it as a zipped file, possibly that may work. Anyway, I sent the same file to Diana of your support team, so she should have access to it.
Ray
I sent my RM10 program file to your support team (Diana) and she replicated this issue. I’m attaching the same file to this email that I sent to her. Also, as I’ve mentioned, your team stated that this has been a known issue, so I’m not the only one who’s had this problem. This problem has also been noted in your RM users forum. Your team stated that the problem was caused by the fact that there was a second marriage in a previous generation (Conrad/Cheryl/Denise Doe). Second marriages are extremely common, they should not trigger an error and other genealogy programs handle this tree perfectly.
What’s been most disturbing is that in the responses that I’ve received, the common implication is that this is not really a big deal. It’s actually an embarrasingly bad error, implying that these families are polygymous, so how much worse can it get? I just want to emphasize again, I’m not the only one who’s had this problem.
Ray