I like that we are able to customize what is shown on the charts made in the FTB, but the formatting of the fact location is inconsistent.
For example, one member of my family is showing up like:
John Smith
b. Jan 1 1900,
Toronto, ON, CA
but then his son is showing up like:
John Smith
b. Jan 1 1900, Toronto,
ON, CA
Does anyone know how to edit this or force it to show the location on a new line everytime? I really want to print and share my chart but really want to fix this first!
Thanks for the reply! Thanks for the suggestion but the location is always written in the location field and not accidentally put in the date field but the site seems to treat them as 1 fact and let them run together! This would be fine if the location field was really short, like just a country abbreviation, but doesn't make sense when part of it has to be on a new line anyway.
I'm sending an email to support now. Thanks for the help. :-)
And yes, pure dutch blood. My grandparents names are van der Wal, van der Sluis, Stok and van Warners. :-)
In an email dated 23/05/2013, Daniel from MyHeritage Support wrote back to me in regard to my concerns about the poor functionality of Record Matching, SuperSearch, and the usless Record Detective. I quote part of his email, with my response, dated the same day.
"I understand that you might have had some issues with Family Tree Builder 7? May I ask why are you not upgrading? If it's because of bugs we would be glad if you could specify which ones and I'll try to help you solve them."
Why not upgrade? How much time to you have to listen?
1. File download issues
It's always difficult for an individual user to know if the problem is local (my own computer) or at your end. I'm using a HP ProBook 4510 Intel Core2 Duo CPU P7370 @ 2.00 GHz and 2.96GB of Ram, running WinXP 2002 SP3.
I haven't encountered this number of issues with any other software, especially not PURCHASED software, so I strongly suspect that the issue is with MH.
Where I write "you", I mean "you the company, MyHeritage" rather than "you the rep, Daniel D."
The V7 exec file does not download properly. It required some intervention on your part before I was able to even download the file (7009.exe). This is not a good start
It's very hard to find incremental upgrades. People on the forum have mentioned several V7 builds, but MH makes it hard if not impossible to tell which is the latest. Did your developers ever fix the Upgrade Wizard?
I just went to http://www.myheritage.com/family-tree-builder and the current file is .7107. Is this the latest build? Doesn't matter, it wouldn't download. [Update 4 Jun 2013: Current build seems to be .7108, and it wouldn't download either]
As several people have told you repeatedly, it would be nice to have a version log so we could tell what bugs were fixed in what build. But why do we waste our time? MH may listen, but they don't DO ANYTHING TO SHOW THAT THEY LISTEN.
I am still unable to downoad V7 using FireFox 21.0. The error is: "C:DOCUME~1TomLOCALS~1TempicZh48tQ.exe.part could not be saved, because the source file could not be read. Try again later, or contact the server administrator." (FireFox is a good example of how to do incremental upgrades, BTW. Fast, seamless, never a problem).
In IE8.06.001.18702 I don't get that error...but I don't get the downloaded file either. The file simply never arrives on my hard drive. (And I'm certainly not about to click "Run")
[Update 4 Jun 2013: Tried today with Google Chrome (Version 27.0.1453.94 m) and got this error
That's zero out of three different browsers -- Hmm, maybe it is my system??
Anyway, MH still has not been able to correct the download issues, despite being told of this by many users (I first reported this before 30 Mar 2013)
You do not give mirror sites for the download. Mirrors are common and helpful. Often a file that won't download from the US will download from a mirror in another locale
2. Reports on the forum
Never mind bugs, we're talking disasters. The forums show a number of people encountering lost data, lost notes, slow speed etc. That's discouraging. And you always answer in a private email so nobody ever knows if the issue has been resolved. I think that is a mistake.
You've several times directed users to go into the Register and make changes. Good software doesn't require that.
I have seen NO forum posts from users writing in to say how wonderful V7 is and how glad they are to have upgraded. NOT ONE.
Over this winter and spring I've done a lot of work on the family history preparing for a big family reunion this summer. I don't want to do anything that would jeopardize this work. I save often and backup weekly. An unstable bug-filled upgrade does not appeal to me
I have at the moment no particular use for the key features of V7. I do not use a smart phone or tablet. I can take my laptop along when I go to an archives, courthouse, or library.
Most family histories I've linked to via SmartMatch has been riddled with errors, incomplete, or contain data merged from my tree. No way I want anybody else able to get in and mess with my work.
3. Lack of confidence in MyHeritage, both the software and the company
Consider the atrocious performance of Record Matches, as I outlined earler. It doesn't help that you tell me it's an obsolete system: MH has let me struggle with that outdated system for the two years I've owned V6 and has never issued any incremental upgrade to fix the issue or even had the courtesy to alert me that it's outdated and non-functional. An alert and and apology would have done a lot to improve customer relations.
The testimonials (http://www.myheritage.com/testimonials) are clearly NOT for V7. As I mentioned above, there are NO reports of anybody saying, "V7 is wonderful"
The lack of incremental upgrades to V6 indicates an insensitivity to user concerns and a disregard of known bugs and issues. Yes, you were concentrating your efforts on the big kick to V7, and that was a strategic decision of the company. However, your refusal on the forum to answer the question "How can I revert to V6?" was highly suspicious. PLEASE CONTINUE TO OFFER SUPPORT FOR V6.
The number of issues encountered with v6 that were never addressed or fixed does not give me confidence that v7 will be any better. V7 is bigger, more complex, and known to be buggy = the potential for headaches outweighs any potential benefit at this time.
4. Available alternatives
I can find records quickly and easily at ancestry.com (for a much higher subscription fee, of course, but it's increasingly clear that you get what you pay for)
I can search census and other records free through my local library
The Provincial Archives of Alberta is 40 minutes away and lets me search all Canadian records for a small fee
The local LDS church has a Family History Center where I can research US data (maybe world data, I've never asked)
Let me know!
I could probably go on for some time. Now you tell me three good reasons why I should upgrade. .
Best regards,
The appropriate response would be, "We recognize that you have some valid concerns about V7. Here's what we're doing to address those concerns..." Of course, typical of MyHeritage, I have had no reply whatsoever, [UPDATE: I did receive a response on Jun 6, a delay of twelve days] and no indication that MyHeritage is doing anything at all to deal with any of the issues I raise. They just don't seem to give a damn. V7 seem to be a poor product, so I wish MH would back up, do it right. Fix the bugs and issues in V6.
Thank you for your patience with my acerbic comments. I have your email, and I quote parts of it here:
1) Regarding the exe file download and install issue.
As I said earlier I've been involved in fixing some bugs regarding this matter, and it seems that this mostly was caused due to antiViruses blocking the installation file for some reason. We have made some corrections and some of them were reflected on 7107. We are also working currently on another build.
I just now went to check, and build 7108 does not download. I encounter the same error as before. I recently tried to download this build in FireFox, Internet Explorer, and Google Chrome, and all three browsers failed. I refuse to disable my AV protection to permit the download. Maybe the next build will fix this, or maybe you'll try some mirror sites. [UPDATE: Daniel sent me a link to what appears to be an alternate server; this file loaded successfully. At Daniel's request, I have done extensive testing on this matter, with three different browsers]
If you are familiar with software release you'd know that the first versions have the most bugs, and the later ones have the fixes.
Yes, I am familiar with software release. Before I retired I was working for an IT department testing custom software and writing documentation and user manuals. I'm generally an early user and beta tester of open source software. But I've never seen anything as buggy as your V7. It appears to have been released too early with insufficient beta testing.
2) Reports on the forum
As I've said above, indeed there were a lot of reports for loss of information, but I can assure you that almost every member that complained eventually got his information back. We made a fail safe in version 7 that when you upgrade it will immediatley keep a backup version of your family tree in v6. So you always have the option to go back.
"Almost every member...got his information back." I feel sorry for the ones who didn't.
"So you always have the option to go back" Then why have you consistently and repeatedly in these forums refused to tell people how to revert to V6?
Notes dissappearing - we fixed.
Smart Matches dissappearing was caused due to members syncing as new trees, those we didn't reported that they got back after awhile.
Photos dissappearing - you always have the family site to restore from, and the photos directory to restore from as well.
Individuals dissappearing - You can always use the backup.
You seem to be missing the point that these things should NOT disappear following an upgrade. Have those issues been corrected, so that users do not have to work to recover lost photos or data?
3) Lack of confidence
We do continue support for v6, but you've got to understand that if you complain about bugs we will always recommend you to upgrade to v7 because if we ever fix a bug it wouldn't be a re-run for v6 but a new build in v7.
You're asking me to leave the stable and functional V6 for the bug-filled and highly iffy V7. Not just yet, thanks.
4) Your comments regarding the supersearch
We wrote down all of your bug reports and notes - it took us awhile to get through, and we will try and work on the fixes as soon as possible.
That's nice. It would also be nice if whenever you release a new build you would say, "Build 7109 fixes the following bugs:"
I use a lot of open source software where the developers explain what they're working on, but you're a private company and don't have to tell your customers anything if you don't want to (besides, you have a Marketing Department to exaggerate for you and make all those grandiose claims that your software doesn't deliver).
5) Competition
The "Record Detective" is fairly new in this field, and we are working to improve it.As you have written to us as an issue in point #4 the record detective needs to start finding records from other individuals as well. It also works to investigate on the smart matches, I'm not sure if you confirmed matches and I would be glad if you could let me know.
Basically what it does is to also inspect the smart matches of your individuals and find potential records as well.
"..we are working to improve it." IMO you are working to get it to work, period. Like supersearch, it was released before it was functional.
I don't use Smart Matches. I do look at them, and occasionally I find a match to a tree that hasn't taken all its data from mine, and in that case I might look at the other tree to see if it has cited sources (few do) or has any information that I don't already have (few do). I no longer confirm smart matches because as they are they're a waste of time. A user named J. M. Steen has a good suggestion elsewhere in the forums.
If the Record Detective is examining smart matches, it's not going to find anything useful. The Detective should be examining RECORDS and matching more than the surname. Both it and supersearch should give the option to NOT include other trees in the results AND to exclude specific trees from future searches.
"I just now went to check, and build 7108 does not download. I encounter the same error as before. I recently tried to download this build in FireFox, Internet Explorer, and Google Chrome, and all three browsers failed. I refuse to disable my AV protection to permit the download. Maybe the next build will fix this, or maybe you'll try some mirror sites."
If you would like to help us and investigate this issue further, we would be more than glad to try again.
"Almost every member...got his information back." I feel sorry for the ones who didn't.
These members who didn't are still under investigation and we will do everything in our power to get their information back.
"So you always have the option to go back" Then why have you consistently and repeatedly in these forums refused to tell people how to revert to V6?
We never refused to tell people how to revert to v6, we merely wrote that our members should write our support team if they find an issue in v7 so bad that they would like to revert to the previous version. I even wrote that our support team will be more than glad to help you to revert back to v6 safely.
You seem to be missing the point that these things should NOT disappear following an upgrade. Have those issues been corrected, so that users do not have to work to recover lost photos or data?
Dissappearing of... (as of the 9th of June 2013):
Notes - fixed
Smart Matches - not dependant on us, but our users (not a bug)
Photos dissappearing (from FTB) - under investigation, can be easily fixed by user restoring from local disk
Individuals dissappearing - under investigation, can be easily fixed by user restoring from local disk
That's nice. It would also be nice if whenever you release a new build you would say, "Build 7109 fixes the following bugs:
We are working on making it easier for our members to know our bug fixes.
"I just now went to check, and build 7108 does not download. I encounter the same error as before. I recently tried to download this build in FireFox, Internet Explorer, and Google Chrome, and all three browsers failed. I refuse to disable my AV protection to permit the download. Maybe the next build will fix this, or maybe you'll try some mirror sites."
If you would like to help us and investigate this issue further, we would be more than glad to try again.
I'm willing to help, but not sure what other info I can provide. Sent to you via a support ticket.
I, too, have no use for the 'additional capabilities' of FTB7, and will NOT consider upgrading until I hear nothing but praise. I have previously proposed that FTB6 should be maintained for those who are not interested in FTB7 even if it did work perfectly. My fear is that FTB6 is being allowed to deteriorate, which would be disastrous for me. There is some evidence of that, since some bugs previously fixed have reared their ugly little heads again. Could we have some member support for keeping FTB6 maintained and viable as an option please?
Could it be that FTB7 actually works if you start out from scratch with it? But that is NOT an option for me!
My fear is that FTB6 is being allowed to deteriorate, which would be disastrous for me. There is some evidence of that, since some bugs previously fixed have reared their ugly little heads again.
Ingrid, can you give some examples of "previously fixed" bugs that have reappeared?
Perhaps you have an early build of V6. You can tell which build you have by going to FTB (on your computer, not the online one), clicking Help, then clicking About Family Tree Builder. The title bar will state the version and build.
If you don't have .5638, which appears to have been the final build for V6, you can get it here:
I do have .5634.I tried to get .5638 by pasting the URL you sent http://web009.myheritage.com/public/updates/5638/family_tree_builder_5638_cd.exe. into the Google search box, but all it returns is FTB7! The two problems that were fixed and got unfixed: 1.The minimal formatting that is possible of FTB notes (e.g. spacing between paragraphs) is not carried over on-line any more. 2. For my family tree photos I have a shorthand name with which I store them in my computer folder (e.g. IngridMunchFTB), but change the title in FTB to record name, spouse and parents for transfer as the photo title on-line (e.g. Jany Ingrid Munch wife of Harold Hillel Frank daughter of Johan and Jeanne Ernestine Munch-van Kuyk).This worked perfectly for more than 3 years.Then about 6 months ago, the shorthand title showed up on-line instead of the title with the genealogy info.—obviously the wrong file was being used.I complained and it finally got fixed in January and worked perfectly again.Now for about two weeks BOTH titles have been showing up on-line.Go figure!I have not complained yet, because what with all the FTB7 brouhaha, I doubt if it would get fixed any time soon or at all.
This one never got fixed.You can re-arrange birth order or spouse order all you want in FTB, it will not get transferred on-line.In desperation I have resorted to estimating precise dates and making a note of it.Using the ‘about’, ‘before’ etc. functions does NOT work.
FTB6 can only calculate one sequence of ancestors, even though someone is descended from more than one sibling.I have complained, but it never got fixed.There are lots of cousin marriages, some uncle-niece marriages and one inadvertent father-daughter marriage in my tree, which FTB refuses to record—I had to enter Papa/Husband as two different persons.
Ah, thanks for that explanation. Just click the hot link above, or click here. Then click Save for Save File and note where the file is being saved. That should start the download the .5638 build. You must then find the saved file and run it to complete the install.
I've no idea if .5638 will correct any bugs from .5634 as MyHeritage never tells us that sort of helpful information.
Thanks for all the excellent examples. Some I had encountered, but since they only affect the online version (and not my personal data, which is of prime importance) I consider them not much bother. I too have lots of cousin marriages (though no inadvertent incest) and originally had to have two cards for some people, but I think I solved that by merging the two cards later. Will have to check back and let you know.
I successfully installed .5638. Neither of the two bugs was fixed, but since they are only annoying rather than fatal, I will live with them and keep working around the other problems I mentioned. This latest FTB6-5638 version does seem to work a little faster, though. I thank you so much for your help!
Please tell me how to UN-upgrade back to Version 6 (without losing recently added data)! V7 is a real shocker and I'm not at all impressed.
It's painfully slow, it allows a person to have 2 sets of parents; it STILL doesn't recognise that multiple siblings and spouses can all be direct ancestors; it STILL doesn't recognise dates BC; oh heck, I could go on and on! Not only have former glitches and annoyances not been addressed, there are added glitches. Very disappointing all round.
Also - please tell me how to Ask a Representative a question which isn't in the FAQ. I cannot find any way to do it - is MH making itself deliberately difficult to contact for help?
Please tell me how to UN-upgrade back to Version 6 (without losing recently added data)! V7 is a real shocker and I'm not at all impressed....
Also - please tell me how to Ask a Representative a question which isn't in the FAQ. I cannot find any way to do it - is MH making itself deliberately difficult to contact for help?
Daisy, to get your V6 back, click here. Then click Save or Save File and note where the file is being saved. That should download the V6.0.0.5638 build. You must then find the saved file and run it to complete the install. I have no idea what will happen to data saved in V7, so try this at your own risk.
How to contact MH is not a big secret, but it's sure hard to find. At the bottom of your family history site (online), scroll all the way to the bottom (or press CTRL-END). At the right, click on "Our blog". When the blog opens, scroll down (CTRL-END), then look at the bottom of the page at the left and click "Contact Us".
I'll make it easy for you: click here. You can then fill in the online form, which from all accounts nobody reads, but at least it will make you feel that you have communicated.
To contact a representative more directly to ask about restoring V6, or about other non-FAQ items, email support@myheritage.com. Be patient, be prepared to wait up to two weeks for an answer, because they're trying to cope with all the bug reports from V7 and I think they're a bit backlogged.
After two weeks, as a last resort, or just for fun and to see who if anybody will respond, email any or all of these addresses:
Thank you. I found out (the hard way) that you lose any data added in V7 once you revert back to V6. Luckily I did a GEDCOM before committing myself to the change. (NB My tree is NOT online)
Is there anything RIGHT with V7? I can't even do a relationships check without the thing crashing.
I have downloaded and installed the 7 version: which I just overlaid over the 6 version.
1. I have received a message:
'Some inconsistencies in the data of project ___________ were found and were fixed by Family Tree Builder. Click OK to save the project with these inconsistencies fixed (recommended). Note: A backup of the project will be created automatically.'
I do not want FTB to fix anything. I cannot locate in Options, General: where you can uncheck the automatic fix of FTB? Can this process be overridden so FTB cannot fix anything? I unchecked the box and exited the program: not saving the automated changes. I perform a backup of the project and GEDCOM after each sitting: so I have the last program saved on my USB stick. (A strong suggestion to Tech Support of FTB program would be to inform the user of what changes were made to their program!)
Can someone please assist with this problem?
2. FTB7. Book reports. I was able to perform a book report on anyone in the tree with V6: now with V7:
Same thing happened to me. I'll be watching for an answer. I have a case where a father unwittingly married his own daughter and they had offspring. The consistency checker will not let me show that in FTB6, so I had to put the father/husband in the tree as 2 different persons.
Just installed FTB (latest version). It downloaded my tree from MyHeritage which has less than 350 people in it & no images. On first attempt at sync the process hangs at 96% of Phase 1 of 4. Eventually the window clears and I get the message to check the sync log. The sync log is not very helpful (to me). Below is my message. What next?
Sync Started at 02 JUN 2013 19:22:53 GMT-8
Sync has failed. Cannot communicate with the synchronization process.
