I am experiencing a curious issue with a date field in the cloud (didn't hav

I am experiencing a curious issue with a date field in the cloud (didn't have this issue before migrating to the cloud). When a user physically enters a date that is "incorrect" (i.e 2/31/2012 or 2/3/960) it is automatically converted to a "valid date" instead of flagging it as invalid. 2/31 is changed to 3/2 (knows it is a leap year) and 2/3/960 is converted to 2/3/0960 (I am not that old - tho I look good for 1052!). This latter one becomes a problem when the text() function is used as anything with a year before 1000 throws a "bad epoch" error.

The behavior I really want is for any invalid date to throw an error in the form and not try to guess what I really meant. If the data entered is allowed to be "wrong" then we open ourselves to a data integrity issue. Before moving to the cloud, I would get an error on 2/31 or entering 960 as a year....

OriginalPostID-31999

OriginalPostID-31999