It gets worse. I added a spouse to each of the two children in my extended version of @kevinm 's test model, each with a single parent. Dragged Husband Family1 to a new database along with everyone in the same tree. That’s 10 people initially but 11 are reported as copied. The phantom shows up as a spouse everywhere there is a single parent and as a child of an original Child2 Family1 and the lineage is screwed up. The phantom has four spouses (all the former single parents) and the lineage is now looping. Compare:
That’s scary. I saw something similar when I experimented with copying one of my trees to an empty file. I’ve submitted this to Support, with a copy of my database and a list of several of the trees that grew when copied. I included a mention of this discussion so that Support would know that others have replicated the problem. I hope a fix will include some way to detect and remove the headless that are already out there, infecting people’s databases. Sort of like a zombie invasion in the movies.
In case anyone is wondering, the latest update (10.0.6) doesn’t fix this problem. I didn’t really expect it to - it hasn’t been that long since we identified it. But I did install the update and tried copying a few trees that triggered the error before and nothing has changed.
Corroborating that the 10.0.6.0 Windows 32-bit version on Win 10 onmy computer still misbehaves as described earlier in this discussion when doing a drag’n’drop of “everyone in the same tree”. I note that if you go through the “Select from a list” and Mark “everyone in the same tree as the highlighted person”, no ‘headless’ person is created by the drag’n’drop.
Tom, are you saying that you get different results when you select the “Let me select people from a list” option from the drag and drop window and then Mark everyone in the same tree using the Rootsmagic Explorer window than when you choose “Everyone in the same tree” from the initial drag and drop window?
Yes. It seems as though they have procedures that differ in some way that gives rise to different result. One may make a list of people first before copying over while the other may copy over the highlighted person and then navigate their tree, transferring at each node in the network. That’s just a wild example to illustrate my hypothesis.
That’s a great find. Hopefully it will help fast track a fix.
@rzamor1, Apologies for the alert but I know that the team is working on a quick update to fix some issues with 10.0.6 and want to make sure that Tom’s discovery that this Win-32 drag and drop issue does not occur if using Explorer doesn’t get lost in all of the weekend activity.
While the comparison between the methods of drag’n’drop of everyone in the same tree has only been reported by me and I am using Win32, the fault resulting from the direct selection has been reported by one or more Mac users and I forget whether it was also observed by a Win64 user in this thread. Note that there are other users of Mac and Win64 who could not reproduce the faulty behaviour.
Thanks for that reminder Tom. The most embarrassing part is that I’ve re-read this thread several times and still managed to overlook the fact that the original issue occurred on mac. Still a good find but perhaps not a quick fix.
