Plus, RootsMagic has figured this all out…we sync constantly, and there’s never red/orange/green OR corruption. I’ve worked with data replication since 1997 and every tool has a non-destructive method of committing data, and backing out changes if there’s failure/corruption. Their sync process HAS to be robust enough to not commit records until the system has no risk of corruption. It really seems that this corruption is happening during FamilySync, and if that’s completely inexcusable. We have to restore, and repeat the process. ![]() After two months of work, the database corrupted, and we started a cycle of restoring databases, and getting about a month’s use of Family Tree Maker, and then hitting corruption. About 6 months ago we had to start over and re-download the tree from Ancestry, which destroyed all of our source citations. ![]() First, there was the months of “Orange” sync status late in 2017 (which we missed, luckily, because we’d kicked them to the curb). ![]() Since going back to Family Tree Maker, it’s been one disaster after another. So, we still use RootsMagic for our 60+ speculative trees, but we went back to using FTM for our main, public tree. When we run a TreeSync with Ancestry, everything went off as expected, but it created 3 separate copies of the same citations…one for each fact. Additionally, there’s no central place to manage/edit/view all sources for a tree, which makes it VERY hard to update citations, etc. The way RM manages citations just isn’t workable for how we support facts in our trees. For example, we created a custom citation in RootsMagic for the 1900 US Census for Roman and Mary Jones and copied the source to each of the 3 Roman’s facts supported by the citation (Name, Birth, and Residence). And we still use/love RootsMagic…but… “Thank you for stopping your work and spending an hour backing up your data, but our TreeSync is so fragile it’s best you put off more research for another 2 hours or so because we don’t know how to design state-aware data synchronization” Didn’t we give away free copies of RootMagic to readers who’d paid for the FTM upgrade last August when MacKiev couldn’t get their act together? We did. We’d never support this horrible effort, with so little partnership from the vendor.Īnd, for you loyal readers, you might be asking why we’re using FTM anyways. And if this was product was deployed in the large corporate environment I currently manage for a Fortune 50 company, we’d pull it out. It would have been a hard year, but at least we wouldn’t have wasted that year hoping that MacKiev could actually create/support software.įirst off, let me say that I have a LOT of experience working with software delivery…with both commercial products and deploying/supporting in-house developed software. We’re starting to think that it would have been better to let Ancestry kill the product off. But nearly a year since MacKiev finally delivered their FamilySync, it’s still buggy and unreliable. Companies like RootMagic have delivered sync without issue, and without risk. ![]() FamilySync has been a COMPLETE disaster since the moment it was promised (then delivered 4 months late), with MacKiev choosing a synchronization strategy that creates data corruption. It’s strong language, but their product continues to be literally dangerous to your data. It’s been a year since MacKiev’s Family Tree Maker dominated this blog, as they struggled to deliver their first version since they took over from Ancestry, and this is what we’ve learned: MacKiev’s Family Tree Maker is garbage. Everything we discuss is our opinion alone, and we talk about it because we use it. One quick point, as always, we receive no financial benefit or consideration for any product or service we review/recommend/discuss here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |