The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

Question

Post reply

The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

Ramalingam S

Mr or Mrs. 500

Points: 550
More actions
June 24, 2009 at 3:29 am

#211224

Hi All,
We have developed a web appln using ASP.Net 2.0 / Sql Server 2005. In a web form, while inserting a value into a date field , I am getting the following error.
"The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value. The statement has been terminated."
We are sending the value in MM/DD/YYYY format from the application.This works in my development environment but not in the production server.
The language assigned to the Sqluser is "English" in both the cases. We don't have access to the production server.
What could be the problem? Kindly throw some light on this.
Thanks in advance

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

joeroshan SSChampion Points: 10377 More actions · Answer 1

try

convert(datetime,'date',101)

----------------------------------------------------------------------------------------------------------------------------------------------------
Roshan Joe

Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help[/url]

Ramalingam S Mr or Mrs. 500 Points: 550 More actions · Answer 2

Hi,

Thanks for u'r quick reply.

I think you have understood differently. My problem is "while inserting , i am getting the sql exception". But this is happening only in production server.

I can't use the convert function because, i have around 50 pages in my application and have to use this convert function everywhere.

Since it is working in my local server, I think this problem is due to some server settings.

Please tell me where to change this settings...

joeroshan SSChampion Points: 10377 More actions · Answer 3

Please see the below link

http://support.microsoft.com/kb/173907

----------------------------------------------------------------------------------------------------------------------------------------------------
Roshan Joe

Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help[/url]

Florian Reischl SSC-Dedicated Points: 37301 More actions · Answer 4

A hint for future projects and implementations...

Don't create dynamic SQL statements containing values in your font end. This enables SQL injection and causes problems as your current. Use parameterized statements and you cannot run into those problems.

///=======================================================

// WRONG WAY

using (SqlConnection cn = new SqlConnection("MyConnectionString"))

{

cn.Open();

string statement = "INSERT INTO MyTable (Id, MyDateColumn) VALUES (1, '06/24/2009')";

using (SqlCommand cmd = new SqlCommand(statement, cn))

{

cmd.ExecuteNonQuery();

}

///=======================================================

// CORRECT WAY

using (SqlConnection cn = new SqlConnection("MyConnectionString"))

{

cn.Open();

string statement = "INSERT INTO MyTable (Id, MyDateColumn) VALUES (@Id, @MyDate)";

using (SqlCommand cmd = new SqlCommand(statement, cn))

{

SqlParameter paramId = cmd.Parameters.Add("@Id", SqlDbType.Int);

SqlParameter paramMyDate = cmd.Parameters.Add("@MyDate", SqlDbType.DateTime);

paramId.Value = 1;

paramMyDate.Value = DateTime.Now;

cmd.ExecuteNonQuery();

}

Flo

MMartin1 One Orange Chip Points: 27795 More actions · Answer 5

Your database login may have a default language different than English, or the production server's default language may not not match the one to your login. Maybe the agent for the job has another default language as well. Either way default languages may not be matching. It is thus best to always use the universal yyyymmdd string format for dates.

----------------------------------------------------