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, 126.96.36.1997.
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.