Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Access 2003 VBA (Used Immediate Window)
? CDate(39870) Returns: 2/26/2009
In SQL Server 2005 (SQL Server Management Studio)
SELECT CONVERT(DATETIME, 39870) Returns: 2009-02-28 00:00:00.000
Do they always differ by 2 or is there some other date setting I’m missing?
Server Collation = SQL_Latin1_General_CP1_CI_AS
Different languages and systems use different numeric representations of dates.
SQL 2005 counts the number of days from 1/1/1900:
Excel and Access VBA count the number of days from 12/30/1899:
Others count the number of days, seconds, or sometimes milliseconds from some other seemingly-random starting point. I think MS DOS used Dec 31st, 1990. UNIX uses 1/1/1970.
So don’t try to translate them directly (numerically, that is). You’ll have to translate to an actual date representation (01-03-2009) and then back in the other environment.
Edit: VBA has some funny quirks about backward compatibility and leap-year calculations. See Joel’s first encounter with Bill Gates for a good read.