@rzamor1 , Now finding examples of lineage corruption caused by drag’n’drop that is not ghost-like and is not cleaned up by Clean Phantom Records. Referring to the examples I posted in RM10 Issue with copying.
Not cleaned.
Not cleaned.
Cleaned in the above case where drag’n’drop was into an empty database,
but
Not cleaned where DnD was into an existing database and there was an existing person with the same RIN as her mother, making her mother a male born after she was.
Cleaned in that empty database target
but
Not in the intended target where she got new, impossible parents from the existing database who are her age-peers, and a whole new lineage.
Cleaned in the empty database target. What the RM cleaner did was to replace the erroneous RIN for the non-person spouse with 0 and that results in the name “Unknown spouse” appearing where it normally would instead of blank. The couple events stay on the known spouse’s profile.
Not cleaned in the non-empty database target which already had a person with RIN=25218 so he got a new completely wrong ancestral lineage.
I don’t know how one can find the uncleaned corruption. Problem alerts may find some but not all and is masked by many that already exist. If the bug originated with the first release, there are potentially many large databases that have been affected.