Created attachment 115692 [details] screen shot It seems for me that the Month December "is forgotten", the January only have 28 Days or 29 in leap years like normally only February has. Please take a look at the attached screen shot or the attached Database. If you open the attached Database, - go to tables - open table "datum" by double-click - manually change the first row "Datum" to 31.12.2014 where ID = 0 - leave the row -> date switch to 31.01.2015 This goes back until 01.12.2014 switches to 01.01.2015. If you insert 30.11.2014 the displayed Date stays. - manually insert into "Datum" 29.01.2015 - leave the row -> date switch to 01.02.2015 - insert into “Datum” 29.12.2014 - leave the row -> date switch to 29.01.2015 Do it until 31.01.2015, the date always switch to the begin of February. After January seems to be OK. If you work with the date-function like DATEADD it is the same behavior of the date. If I use the following SQL Statement in Tools/SQL... UPDATE "datum" SET "Datum" = '2014-12-31' WHERE "ID" = 0 and make a select "Datum" from "datum" WHERE "ID" = 0 the output returns 0114-11-31 I use Win 8.1 and attached the Base file
Created attachment 115693 [details] Sample Database
Confirming on Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Locale : fr_ OSX 10.10.3 with test odb file supplied by reporter
Already present in Version: 4.3.5.2 Build ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5
See the same problem in Version: 4.2.4.2 Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8 so it has probably been there since fbembed support was introduced
It is probably a duplicate of Bug 91324 and needs retesting. It seems to me the issue is not present any more. Version: 5.3.0.0.alpha0+ Build ID: bd28d789d0bfde255cfeef9422ddb816e3d57248
*** This bug has been marked as a duplicate of bug 91324 ***