I have used RM versions occasionally in the past so I am a real novice when it comes to RM.
I have recently installed RM 10. I downloaded my main tree from Ancestry (huge).
Everything has been going fine (sync etc.)
As my main tree on Ancestry has now caught the dreaded “database error” when syncing with FTM, I want to totally dispense with FTM delete that tree and now only use the RM 10 tree.
That’s where I am stumped. I have followed the suggested instructions but when tree share opens it just does the sync routine. I can’t find any way to start a tree upload session.
Joe, I like you moved (migrated) totally to RM 10 and it has been a learning experience as RM has a different heuristic perspective. From what I have learned, with the help of those here, is that you want to disconnect your RM file from the Ancestry. After this is done, you will want to export to Ancestry with a different file name. Then the uploading will be started and finished. Now as you update your RM file, TreeShare will only do one person at a time and have to confirm each change, which is long to perform. I have taken the approach to get my RM File in a “good state” by my standards, and then I will export to Ancestry. Just sharing what I have experienced, learned, got an understanding of doing, and how I have developed my strategy.
Thankyou Franklin I will give it a try. I found the sync operation the hardest to learn but I think I have it now. It is perhaps better to chose each and every change in case of error.
to maintain changes was your RM database is linked to Ancestry you basically have two options. You “shared/sync” each of those changes one by one (unlike FTM you can not do all at once – which is good think as you do not get the errors you experienced with FTM. I left FTM (after using for 17 years) for that reason and been RM since. I do not try to maintain most changes. Several users and myself include instead == upload to a new Ancestry Tree every so often – for me this is about twice per year. This does not work for everyone – but I mainly use Ancestry for hints so it works for me.
Kevin
After having be a long time FTM user, at first I found it awkward and not making sense. I worked through it, got the logic down and now am a firm believe of this approach.
As said, I am now with that practice. Only loss that I see is that sharing an Ancestry file will lose the sharing links each time. But to be honest, after understanding the processes and practices, it makes sense to do it this way.
I want to suggest an slightly alternative approach for consideration, since the action to “disconnect” your RM db from Ancestry is irreversible. Rather than disconnecting your primary RM db, make a copy of your RM file and disconnect this copied file from Ancestry. You can then upload a complete ancestry tree from the new RM copy. The only difference is that the master RM db is still connected to it’s ancestry file with the status of hints intact, etc… I mark the ancestry tree connected to my master RM db ‘private’ and push a public version up when there are significant changes. This may or may not be helpful depending on your specific workflow.