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 |
|
jeffjohn
Starting Member
2 Posts |
 Posted - 2005-03-08 : 01:57:43
|
Greetings, I am having the following problem on one of my web application deployment. The details of the deployment is as follows.We have an application which is developed on ASP.Net and the development environment was on Windows 2000 professional.After the development,we tested the application on Windows 2000 Advanced server and it runs perfectly fine whiout raising any issue.During the deployment, where the Web Application is delpoyed on Windows 2003 Server with IIS 6 and the datbase is on another Windows 2003 Server. Both servers are kept under a DMZ. The application works perfectly fine for retrieving the information.While submitting any form which has a date field, system throws an error as shown below."The statement has been terminated,The conversion of a char data type to a datetime datatype resulted in an out of range datetime value"Please help me to solve this issue.Jeff  |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-03-08 : 05:16:25
|
| You are probably using character dates with format dd/mm/yyyy, mm/dd/yyyy, yyyy-mm-dd.All of these can have region problems with sql server. If you use yyyymmdd then the problems will go away.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
jeffjohn
Starting Member
2 Posts |
Posted - 2005-03-08 : 07:04:07
|
| I have tested this application by loading on Windows 2000 server and the application runs smoothly without any error.The application started raising the issues only after moving to the production server which is Windows 2003 Server. I kept the same configuration for both the servers. |
|
|
|
AndyB13
Aged Yak Warrior
583 Posts |
Posted - 2005-03-08 : 07:55:58
|
Are the default language settings the same on both SQL serversIn EM right click Server >> properties >> server settings I agree with Nigel - yyyymmdd gets rid of any ambiguityAndyBeauty is in the eyes of the beerholder  |
|
|
|
|
|
|
conversion of a char data type to a datetime