The connection to the Ancestry tree is inside the database. So it won't matter what computer you are working on.
Thanks Renee. Good to know. I was thinking of reinstalling RM because of the freezing problems with TreeShare. However, that seems to have been resolved. At least it has not recurred lately.
My other problem (not being able to update Ancestry from RM through TreeShare) is still an issue. As I knew would be the case, when you reconnect your RM tree to Ancestry, Ancestry resets (or reopens) all the hints you have previously worked. I tried to reaccept/or reject these hints using WebHints, but the action would not take. RM still showed the hint open (bulb on) and I have had to do it on the Ancestry side. RM will then display the correct hint status. This has to be done for every person (hint) in the tree.
In addition, if an event/fact/note/or source needs to be replaced or changed, TreeShare will not transfer the data from RM to Ancestry unless the Ancestry hints (that were reset because of the RM tree being reconnected to Ancestry) have been reaccepted/ or rejected first. In other words you have to reassociate sources, notes, and media to each fact or event where you previously accepted an Ancestry hint. This means essentially "starting over" with each person in your tree where Ancestry hints are involved.
I am currently reviewing all members of my RM tree, against my Ancestry tree, and I am re-accepting/rejecting all hints that were reset by the re-load of my RM tree. This then allows me to share data from my RM tree back to Ancestry, once again.
I have noticed that any new hint (not acted upon prior to the database reconnection to Ancestry) seems to work fine. This indicates that there is some sort of broken links caused by the reconnection hint re-set.
Had I known just how big of a problem all this was going to be, I never would have re-loaded my RM Tree to Ancestry. Anyone thinking of doing this should carefully consider the consequences.
Thank you for your help