tracker issue : CF-4200715

select a category, or use search below
(searches all categories and all time range)

Change cutoff year for createodbcdate() and createodbcdatetime()

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): John Walker / John Walker ()

Created: 01/17/2018

Components: Language, Functions

Versions: 11.0

Failure Type: Others

Found In Build/Fixed In Build: /

Priority/Frequency: Normal /

Locale/System: / Win 2008 Server R2 64 bit

Vote Count: 0

If you convert a user entered date of 12-31-30 using createodbcdate() the resulting date is 1930, not 2030.   That is only 12 years from now.  SQL Server and other software I am aware of has a cutoff of 50, and that will surely be modified soon to push the date back even further.  SQL Server has the cutoff year in the Properties of a database.  It would make sense to me to default a CFADMIN setting to 30, but allow users to override it.



Repro code: <cfdump var="#CreateODBCDate(createDate(30, 12, 12))#">
Comment by RAHUL U.
128 | January 17, 2018 08:11:46 PM GMT