Saturday, January 25, 2014

conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value

As suggested here, this problem in Entity Framework stuff basically stems (most likely) from handing in an unassigned DateTime value which ends up being translated to day one of year one which is only legitimate in datetime2 formatting.

No comments:

Post a Comment