conversion of a varchar data type to a datetime data type resulted in an out-of-range value

Question

0.00/5 (No votes)

See more:

Actually i created one ERP project...it's complaint management system based...while some inserting the values in my asp.net page i getting this conversion of a varchar data type to a datetime data type resulted in an out-of-range value error...but for this error i made changes in sql server i change into login---->ONDEMAND\bench(user) i change the language into dutch..its getting clear now...but while i putting reports i getting same error....so again i change into dutch---->english means i can get clear but again stuck on the first one????

How to solve this problem????

Posted 15-Oct-13 3:37am

Deenuji

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Stephen Hewison · Answer 1 · 2013-10-15T03:56:00

When you change language in software you're often changing more that just the language.

You are telling the software to conform with the culture of that language.

This means that the way dates are written change.

en-GB has a date formation of dd/MM/yyyy
en-US has a date formation of MM-dd-yyyy

Not only are the delimiters different but the order of the date components changes too.

So where as an input of 13/11/2013 would work for a en-GB culture. This would throw an exception for the en-US culture as there's no 13th month in the year.

Check the date culture for your desired language and ensure date inputs match the expected format for that culture.

Failing that, always try and convert to a UTC date format before providing the date to SQL.

mprakash12 · Answer 2 · 2013-10-15T04:16:00

Solution 2

Use this

Format(Now, "yyyy-MM-dd")--- in vb.net code
Strings.Format(DateAndTime.Now, "yyyy-MM-dd")--- in C#

Posted 15-Oct-13 4:16am

mprakash12

Comments

Member 12521230 19-Sep-17 7:50am

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