Jump to content


Photo

Error: TTaskDialog requires Windows Vista or later

TreeShare Mac Vista

  • Please log in to reply
8 replies to this topic

#1 Quinnat

Quinnat

    New Member

  • Members
  • Pip
  • 1 posts

Posted 27 August 2017 - 12:14 AM

I get this error message when using the TreeShare for Ancestry window. I can reproduce it consistently on clicking the button "Options" and choosing "Clear everyone from changed list". (I did get the same error message doing a different function within TreeShare but don't remember exactly what it was. Most likely it was while syncing one individual.

 

I am using RootsMagic for Mac version 7.5.3.0 (25 Aug 2017). Because of this error I can't use TreeShare with the Mac version. (Tried same thing in Windows 10 with no issue.)

 

Has anyone encountered this and, if so, found a solution?

 

 



#2 Renee Zamora

Renee Zamora

    Advanced Member

  • Admin
  • PipPipPip
  • 8726 posts

Posted 28 August 2017 - 05:06 PM

Confirming this issue has been reported to development. 


Renee
RootsMagic

#3 ftipple

ftipple

    Advanced Member

  • Members
  • PipPipPip
  • 76 posts

Posted 30 August 2017 - 04:15 AM

The same thing happens to me if I try to delete someone in Ancestry via the Treeshare option

#4 Renee Zamora

Renee Zamora

    Advanced Member

  • Admin
  • PipPipPip
  • 8726 posts

Posted 30 August 2017 - 03:01 PM

That issue has also been reported to development.


Renee
RootsMagic

#5 jmorton05

jmorton05

    New Member

  • Members
  • Pip
  • 1 posts

Posted 15 November 2017 - 12:00 PM

Renee Zamora

Can you tell me if there is an ETA on this issue, or a work around?  At this point, the inability to reconcile my tree with Ancestry is show stopper for using Roots Magic in any meaningful way.



#6 Renee Zamora

Renee Zamora

    Advanced Member

  • Admin
  • PipPipPip
  • 8726 posts

Posted 15 November 2017 - 03:32 PM

I don't have an ETA this is actually being worked on by the Codeweaver team that makes the wrapper around the Mac version of the program. If I recall correctly (not on my Mac right now) you can use the button to clear an individual from the changed list. Its in the upper right corner on TreeShare. To the right of the Options button. 


Renee
RootsMagic

#7 Albert9463

Albert9463

    Member

  • Members
  • PipPip
  • 5 posts

Posted 21 November 2017 - 11:11 PM

As Renee mentions above, the issue is not Rootsmagic 7 for Mac (although a native OSX version would be nice :) ) but an issue between CrossOver (CodeWeavers) and MacOSX High Sierra, and as I understand it, its an OSX issue rather than CodeWeavers. The MyHeritage Family Tree Builder package flat out refuses to work at all. It just gives an error message then shuts down. There are a lot of apps for Mac using CrossOver that are having problems with High Sierra. 



#8 rlaney

rlaney

    New Member

  • Members
  • Pip
  • 1 posts

Posted 02 March 2019 - 04:27 PM

This was originally posted in August 2017 -- it's now March 2019 and I am having the same issue. Is there a fix? I discovered 47 people that need to be deleted from my tree. Since it's easier to do so on RootsMagic 7 for Mac, I deleted them there and planned to remove from Ancestry using Treeshare. The two trees are properly connected and RM ran the comparison and found the discrepancies. However, it will not permit me to reconcile them by removing them from the Ancestry tree via RM.

 

After the time it took for me to delete from RM, plus the time it took troubleshooting, now I have to delete from Ancestry manually. Such a waste of time. I tested it the other way around -- delete from Ancestry, run Treeshare, then delete from RM -- and it does not work either. Same error message. You can add people to either tree via Treeshare, but you cannot delete.

 

I tried to include a screen shot of the error message in this post but, of course, I got an error message on this site too ... LOL. Not my day I guess.



#9 keithcstone

keithcstone

    Advanced Member

  • Members
  • PipPipPip
  • 141 posts

Posted 15 March 2019 - 08:36 AM

I've done the upgrade to the newer CrossOver wrapper and am running the latest version of RM, and the problem still exists. I am guessing it won't be corrected until RM8 comes out.