Detecting corruption from RM10 Drag'n'Drop
I'm especially grateful to Tom since the initial response I received from RM was a brushoff ("here's how to unlink duplicate parents"). When I persisted, Renee said my databases were both corrupt; they weren't. I posted a question here about Renee's statement to me that "Even just opening the database in SQLite could have messed with the tables there." That's when Tom got involved.
I don't know how much overlap there is between the RootsMagic Facebook group and the community forum. I'm going to post links to the forum discussion in the FB group and warn people about the drag and drop issue.
overlap there is between the RootsMagic Facebook group and the community forum.
yes there is -- for more serious questions I would say the Community board forum would be better. I think most causal users use the FB group out of a matter of convenience.
It is not a good feeling when one is dismissed and its nice to not you are not crazy.
Kevin
For anyone who would like to replicate the drag'n'drop test on any version of RM or other software with the smallest files, attached is a zip file with two GEDCOM files and instructions. This will demonstrate the potential corruption if you have done a drag'n'drop transfer of Descendants using RM 10.0.3.0 and possibly (probably) earlier updates going back to 10.0.0.0.
Uploaded files:Quote from Richard Otter on 2025-01-27, 12:59 pmAny comment from RM Inc?
I emailed the RootsMagician around 2200 AST and received a prompt reply saying he thinks he has identified the source of the problem and hopes to have a fix ready for testing by Renee tomorrow.
I emailed the RootsMagician around 2200 AST and received a prompt reply saying he thinks he has identified the source of the problem
cool. To credit RM team the -- logic of drag n drop logic/code involved is quite complex an one simple error can cause issue but identifying and replicating issue certainly helps narrow where to look (usually).