(from SQL Server Books Online):
datetime
Date and time data from January 1, 1753 through December 31, 9999, to an
accuracy of one three-hundredth of a second (equivalent to 3.33 milliseconds
or 0.00333 seconds). Values are rounded to increments of .000, .003, or .007
seconds, as shown in the table.
smalldatetime
Date and time data from January 1, 1900, through June 6, 2079, with accuracy
to the minute. smalldatetime values with 29.998 seconds or lower are rounded
down to the nearest minute; values with 29.999 seconds or higher are rounded
up to the nearest minute.
So make sure you use datetime if you don't want to run into the year 2079
bug!
-----Original Message-----
From: Tyler Silcox [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 11:39 AM
To: CF-Talk
Subject: RE: cf_sql_date
Err...yea, you right. I didn't see the cfsqltype type.
You need to use the cfsqltype cf_sql_timestamp type for MSSQL, but you also
have to have datetime as your column type in MSSQL if you want the date and
time...instead of just smalldatetime, etc.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
