Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2000-09-13 : 14:20:47
|
Joel writes "We are inserting a date that goes through this path:
1. From an ASP page.
2. to a COM component
3. to a Stored procedure that stores this date...
my problem is that any date before 1950, it will convert it to something like 2049...even if we physically insert a year that has 4 digits...
I know that there is something about the "2 digit year cutoff" that will make that assumption for you if you enter a "2 digit year"... but all the documentation I've seen says that if you enter a 4 digit year...you wont have the issue.
how can we avoid this?
Thanks
joel
info:
SQL Server 7.0
windows NT 4.0 Server"
|
|
|
|
|
|
sql server dates...it assumes too much