SQL datatime convertion error

Question

0.00/5 (No votes)

See more:

I have received following error while submitting form in local.

SQL

Microsoft OLE DB Provider for ODBC Drivers error '80040e07'

[Microsoft][ODBC SQL Server Driver][SQL Server]The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.

/AboutUsInput.asp, line 102

i am inserting date using

MM_editCmdA.Parameters.Append MM_editCmdA.CreateParameter("param8", 202, 1, 255, Date())

My system datetime format details is

‎August ‎17, ‎2012
7:40:50 PM
time zone--(UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi
Format:English(United States)

this works properly in other machines.

Posted 17-Aug-12 4:14am

Ritesh Rana

Updated 17-Aug-12 10:47am

Wendelius

v3

Add a Solution

Comments

Maciej Los 17-Aug-12 18:02pm

Before "INSERT" section add SET DATEFORMAT ymd; command and see the result.
More on MSDN: DATEFORMAT

1 solution

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)

Christian Graus · Accepted Answer · 2012-08-17T05:14:00

So what is different ? You're saying it blows up on a different client machine with the same SQL Server ? Then your date format must be different somehow.

However, the fact you call date() means you're getting the date on the server. I don't see how this could work today on some machines and not others. I think you must mean that it works on different SQL servers. In which case, the issue has to be with your date format in SQL Server, or on the target machine itself.