I’m a long-time user and suddenly am having a conflict with TreeShare. I connect w/TS and Ancestry shows sevens people with no match in RM . . . but those seven already exist in my RM database. I’ve tried adding them anyway, then going to RM and merging the seven with their new “doubles.” When I link to TreeShare again the same seven show up. Again with no counterparts on RM to link to. These seven names are the only ones that appear. Not sure what to do.
Could those seven individuals have been added through a drag n drop in an earlier version?
We fixed an issue earlier where drag n drop between two databases connected to different Ancestry tree would cause the person to still be linked to their former tree. There isn’t a way to remove those link unless you disconnect the whole database. The best option is to drag and drop those seven individuals into a new database. Disconnect the small database from the Ancestry tree. Delete them from the main database and then drag them back over.
Is this happening with the latest version?
Thanks, Renee. I think I solved my own problem. In TreeShare, I alternated between “show only changed” and “show all”; I isolated the seven problem folks, then either linked them or deleted the extra copy in Ancenstry. These seven never showed up as duplicates in Ancestry itself, but did appear twice in TreeShare in the “show all” list — one entry paired with its counterpart in RM and one standing alone. I can’t explain this but I seemed to have fixed it. Thanks for your attention.