As stated above, we do have an option to merge trees, however this will not automatically merge duplicate people that appear in both trees. Indeed we use the dynamic IDs that the Family Tree Builder creates. I hope that in the future we will be able to offer a smoother merging function that will automatically merge duplicate people that appear in both trees, however we do not have a timetable for this, I apologize.
Regarding uploading new GEDOM files, indeed Smart Matches are recalculated, however there is no need to invite members to the site again, as this applies per site, and not per tree, and the site remains the same.
Again, I apologize about the inconvenience caused.
Thank you for that but where do I find the step by step procedure for updating my site with a GEDCOM file of some 12,500 people with over 200 pictures referenced and some 20,000 events geolocated; so that I minimise the number of "smart matches" that others need to confirm.
a) do I delete my current tree first then import to a tree of the same name ?
b) import to a new tree name then delete the old one ?
c) merge the new with the current where only some 200 entries will have changed and thus give rise to over 12,000 duplicates but only then changes will come as new "smart matches" ?
with a) & b) how do I re-attach pictures without having to do each one individually?
Can you please check whether you have any network security or communications software running on your computer, or on the network which your computer is a part of? This may include firewalls, proxy servers, anti-viruses and/or routers. The presence of such software or hardware may cause problems communicating with MyHeritage.com, unless they are properly configured.
Such software or hardware are more commonly found in office environments than at home.
I have recently noticed a problem when a certain date format is made in places such as Date of Birth, Death, Burial, Christening, etc.
If I use a 'Single Date' format and enter say 'About Feb 3 1556/57' for some reason the system records it and displays it as 'About Feb 3 1554/55'. If I change this and enter 'About Feb 3 1556/7' I get the same result, i.e. 'About Feb 3 1554/55'. This also happens when I use an exact date. Even if I use the Free Format Text option and enter it in the same format as a Single Date would, the result is still the same.
This was never an issue previously and I have just noticed it after I have upgraded to the latest version, 18.104.22.1687.
The way the system handled the date previously is a better option, unless there is something I am doing incorrectly. Please advise if this is a System issue and when it can be expected to be fixed. Many thanks.
I have discovered a somewhat similar problem, but maybe it's just a different convention and not a bug.
I use the Swedish language version of MyHeritage, and here in Sweden we specify dates according to the international ISO standard: YYYY-MM-DD. However, if I enter 2000-05-01 (meaning "first of May"), the system interprets this as fifth of January.
To change the format of the dates doesn't fix the problem. Finnish language dates DD-MM-YYYY turns to be out of a gedcom-file MM-DD-YYYY - f.e. 01.05.2000 (first-of-May) becomes to 5. Jan 2000, no matter if I use english or finnish on FTB. With thousands of dates to fix I'm puzzled :-I
this is why the genealogy standard is either May 1 1995 or Jan 5 1990. When you enter dates to FTB you should enter them in this way, or use the date picker to pick an exact date (the icon of the calendar next to the date field).
If you already have many of these ambiguous dates, I recommend on fixing them this way (not manually):
1 Close FTB
2. Go to My Documents \ My Heritage \ (your project name) \ Databse
3. Back up the .zed file inside, so that you can always go back to it in case of trouble.
4. Open the zed file with WinZip, WinRar, etc
5. Edit the text file within with notepad, or another text editing program.
6. Use the Find and Replace command to replace all ".1." instances with " Jan " (note that you need to replace the two periods with two space characthers, before and after the string "Jan")
7. Go over the file and make sure this change corrected the dates and made them non-ambiguous.
8. Repeat the Find and Replace action 11 more times, once for each month.
The date form such a 1.5.1990 (1st of May) is a standar in Finland and around Europe. When all do it in the same way it's not ambiguous. It was not like that some 100-150 years ago and backwards. To interpret old records from that period is quite tricky 'cos the ambiguous dates. Anyway, the fix you recommended really worked! It's just that dates instead of 1.5.1990 -form were in the form 1 5 1990 (without dots) in the .zed-file, so 12 find-and-replace were not enough but 12x12=144 times (days 1-12 for every month) were required to do it. It took an hour and a half or so, not bad at all I say.
Thank You. And for the others who will possibly have the same problem I say in finnish (so that they can google it out):
Miten saan vaihdettua päivämäärät Family Tree Builderissa oikein päin? Kuukaudet ja päivät ovat väärinpäin.
I have a situation where the woman was married subsequently divorced. No children were born of the marriage.
The woman subsequently had a child out-of-wedlock with another man. They never married.
I'm having a hell of a time trying to show the relationships! Either the software wants to make the child a child of the woman and her ex-husband, which isn't correct, or it wants to make the natural parents married, which they never were.
Surely there must be a way to show that this woman married and divorced with no children; then had a child with a man she wasn't married to, and yet still show the child's natural parents?
If there's no way to do this, then I can't use this software.