Hi, I'm trying to import a GEDCOM into MyHeritage Family Tree Builder. The GEDCOM is generated by Ancestry.com. Ancestors marked as "deceased" on Ancestry.com are coming over as not deceased in MyHeritage Family Tree Builder. I need them to come over checked as "deceased" so that when I split the tree in MyHeritage Family Tree Builder, I can have it correctly select only the deceased people for the split tree. The only option I have right now is to manually go through the hundreds of incorrectly imported records and manually mark them as "deceased" - too time-consuming.
And I cannot figure out how to correct this. All the children and siblings are my wife's, yet they are showing as mine, and I have tried to edit, and can't seem to make the changes. Yes, the help says: 1. Under parents’ personal cards click ‘Edit’ button. Select ‘Children’ and click on ‘Manage children’. Well, I can't find these parents personal cards, and I sure can,t find how to re-assign the people to my wife. My Heritage has not responded, can someone point me in the right direction, please.
Whenever I sync my FTB .. keep getting error message: "There are 36 items (photos, etc) which could not be imported for proper publishing". Has anyone experienced this frustatrating issue ?? (Thanks for any response, Helen More)
I have been having this trouble for the last month, I am also using Xp with version, it was working fine, I e-mailed the Tech team on day, they replied as I was a Premium holder, I would be placed in the priority queue, unfortunately that was a while ago now and still no result.
Is there any way to export a list of persons assigned to each tasks? for example, I can export a list of those I require dates of birth for. I can only seem to export the names of the tasks rather than those attached to that task.
I am incensed!! I can't say that more emphatically. All the posts on here regarding FTB's failure point to a systemic failure on the part of MyHeritage. I'm thinking this is the beginning of the end for MyHeritage and the consumer will be the last to know. What is painfully obvious is that any sort of 'tech support' has vanished since there are no replies from MyHeritage to any of the recent posts.
Due to the obvious concerted effort on the part of MyHeritage to ignore the FTB failure, I will be leaving at the end of my subscription. We (the clients) are treated poorly with system failures and cumbersome changes (i.e. the new Smart/Record Match process). No more! I'm not gonna waste my breath asking for a refund and DO NOT want a gift certificate for future purchases.
I strongly encourage MyHeritage to be more forthcoming with systemc shortfalls, app updates, etc. A simple email or message to 'Dear Subscriber' would be a good start. Transparency is the common thread among all truly successful organizations.
I get this error (or similar) whenever I try to do anything in FTB where it tries to communicate back to the web, ex: update matches, anything under the Family Site button, sync, etc. It acts as if I have no internet connection (which I clearly do have working just fine.) It's been the same for a couple days now. I can access my tree from a browser window just fine so it's not like my account isn't active or something. Nothing at all has changed on my end.
I am really not happy with the limit put on account for my sync. So many times I have tired to sync in January it is failing. Are you telling me now that once a day at a certain time "ONLY" I can sync, because that is horrible! Yesterday it wouldnt sync at all, today it will not sync......so do I need to wake up at the weee hours just to sync?
UPDATE: its been since Jan 13th and I still cant Sync!!!!
Thanks to the creators of this website for the wonderful resource. Could someone please guide me on setting up polygamous relationships in the family tree. I had an uncle who had two wives during his time, I'm having difficulty recording that as the site will only allow a monogamous marriage.
I recently installed FTB on windows 10 under my own Microsoft user profile/login. FTB software is automatically starting in other family members logins prompting them to join or start a family tree. This is intrusive and annoying. How can it be stopped from invading other PC users?
I have a lot of sources that are blank or are duplicates, and I'd like to clean them up. However, the "source usage" button just hangs the software. "Delete source" also hangs the software. Similar problems under Manage Repositories.
Does anyone know how to work around this or fix it?
I am a Premium user, and have the latest version of FTB.
Does anyone else have the following problem or is it just me? I add a Census fact to a person and enter 1841 in the Date, London as the Place and Aged 80 in the Description. I then click OK, but when I go back in the only entries which are retained are Census and 1841. The place and description are not saved. I have had to suspend entries.
I have raised an issue, but am waiting to hear. Anyone else with this issue?
There are several glaring bugs in 8.360 in how places are handled. I have reporting this issue to support but they seem to have gone dark of late.
a) How place names are handled is seemingly random, with some treated as a text string with a limit and others treated as a structured set of fields. The exact same place name is treated both ways with no way to manage how this is being done.
b) When trying to correct place names via the Maps function the bug above causes the update to fail, with the suggested place name lost in the process followed by a lengthy reload of the map to get back to where you were.
c) Using the View -> Places workaround to the 2nd problem avoids the map reload, saving considerable time and frustration but doesn't suggest fixes. It also has the 1st problem where two (or three or four) place names structured identically do not consolidate. If place names are a text stream they consolidate, but if they are structured they do not.
Since there is no practical way to clean up place names on the web site it would nice if this clean-up process would work offline via FTB.