Insert/update datetime from VB6 to SQL server

Question

1.00/5 (1 vote)

See more:

In MS ACCESS
itmarr(0, 0) = "bill_date"
itmarr(1, 0) = TxtDate.Text

IN SQL SERVER
itmarr(0, 0) = "bill_date"
itmarr(1, 0) = Format(TxtDate.Text, "dd MMM yyyy")

ERROR SHOW IN SQL SERVER]
the conversion of a varchar data type to a datetime data type resulted in an out-of-range value

What I have tried:

Insert/update datetime from VB6 to Sql Server

Posted 26-Feb-17 20:32pm

Jitendra shekhawat

Updated 10-Mar-17 2:24am

Add a Solution

Comments

Richard MacCutchan 27-Feb-17 3:33am

The error message is clearly telling you what is wrong. Check the values of your variables to see why.

Jitendra shekhawat 27-Feb-17 4:03am

Please tell me error....??
and how to solution this problem.....
please help...

Richard MacCutchan 27-Feb-17 6:23am

The error is as detailed in the message. And the solution is to check your code and your data to see why it is not valid. Remember, we cannot see your screen so have no idea what information your system is trying to process.

Jitendra shekhawat 27-Feb-17 6:32am

ohk, sir
thanx

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)

CHill60 · Accepted Answer · 2017-03-10T02:24:00

Always try to use "unambiguous dates" when passing information around - especially to and from databases.

What does that actually mean? It means use a date format that cannot be misinterpreted no matter which in country or time zone you're in nor which language is being used.

Example: 01/06/2016 would be 1st June in the UK but 6th January in the USA.

You are pretty close because you have used dd MMM yyyy as the format. Which is fine in most languages ... "27 Feb 2017" works in English, Dutch, German, etc etc but in Finnish would be meaningless (Finnish for February is helmikuu). It's not unusual these days to have SQL Server servers hosted in different countries to the one where the application is running. Nor is it unusual to have users from multiple countries accessing the same SQL database.

There are two formats for dates that are guaranteed to work for all versions of SQL Server. Usefully they work for most other databases as well.

yy-MM-ddTHH24:mi:ss

and

yyyyMMdd HH24:mi:ss

It's also worth having a read up on the ISO standard for dates - ISO 8601 - Wikipedia[^]

If this doesn't solve your specific problem, then put a breakpoint (F9) on the line

VB

itmarr(1, 0) = Format(TxtDate.Text, "dd MMM yyyy")

and have a look at the contents of TxtDate - you'll probably find that it can't be formatted as a date at all. You should really add some validation OR use a DatePicker control.