Jump to content


Photo

Drag'n'Drop breaking TreeShare links to Ancestry Sources

TreeShare dragndrop sources

  • Please log in to reply
3 replies to this topic

#1 TomH

TomH

    Advanced Member

  • Members
  • PipPipPip
  • 6004 posts

Posted 11 January 2019 - 10:06 PM

Warning TreeShare users: do not drag'n'drop from a TreeShare database to a new database if you intend to continue using TreeShare on the new database and will edit source/citations.

Editing certain fields such as the Research Note now triggers a change detection that it does not in the original; updating to the Ancestry Tree results in what was an Ancestry Source also becoming an Other Source.

Why? RM7580 (and maybe some prior updates) no longer copy the Ancestry Source links via drag'n'drop to the new database which then cannot transmit it to Ancestry so that Ancestry recognises the source as an Ancestry Source.


Tom user of RM7550 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com
SQLite_Tools_For_Roots_Magic_in_PR_Celti wiki, exploiting the database in special ways >>> RMtrix-tiny.png app, a bundle of RootsMagic utilities.


#2 TomH

TomH

    Advanced Member

  • Members
  • PipPipPip
  • 6004 posts

Posted 15 January 2019 - 10:53 AM

Absent acknowledgement here or on fb by Renee or a response to my email to the RootsMagician that this is a bug or a regression that will be fixed, I have submitted a Support Request (#76408).


Tom user of RM7550 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com
SQLite_Tools_For_Roots_Magic_in_PR_Celti wiki, exploiting the database in special ways >>> RMtrix-tiny.png app, a bundle of RootsMagic utilities.


#3 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8121 posts

Posted 15 January 2019 - 02:50 PM

I just haven't had a chance to focus on testing this. 


Renee
RootsMagic

#4 TomH

TomH

    Advanced Member

  • Members
  • PipPipPip
  • 6004 posts

Posted 15 January 2019 - 04:33 PM

It doesn't manifest itself as an issue in TreeShare immediately on opening TreeShare after the drag'n'drop. Only when something has been done to the source on the RM side that triggers the detection of a change. That's when you start chasing your tail.

The underlying fault is obvious from an inspection of the LinkAncestryTable with SQLite.

Tom user of RM7550 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com
SQLite_Tools_For_Roots_Magic_in_PR_Celti wiki, exploiting the database in special ways >>> RMtrix-tiny.png app, a bundle of RootsMagic utilities.