Migrating information from Ancestry to Roots Magic

[TomH]

@tcluster

TreeShare was using the permanent version of the database, not the temporary copy created by the relationship chart.

That’s a reasonable supposition. Thinking back to the problem Do not use Relationship Chart until next update else lose data, I would add that RM might be opening and closing multiple instances of its SQLite database engine concurrently and that might be okay because a sqlite database allows multiple readers. But it is supposed to restrict writers to one at a time. I would have expected that the Relationship Charts instance having an incomplete Transaction would disallow any other instance from writing to the on-drive database and that would have prevented TreeShare’s instance of sqlite from writing anything to the database which I think would have to happen if a change is applied in either direction. Maybe the write lock is not applied when the transaction begins but waits until it is committed. Maybe @kevinbenson could clarify what is allowed by sqlite although maybe this is getting too techie for this forum.