string was not recognized as a valid datetime

Question

0.00/5 (No votes)

See more:

I am getting this Error on the webserver suppose if i put the date as 30/12/2012, but it is working in my local machine.

C#

if (row["Approve_Date"] != DBNull.Value)
{
    DateTime aprRecDate = (DateTime)row["Approve_Date"];
    if (aprRecDate.ToString("dd/MM/yyyy") != "01/01/1900")
    {
        txtAprvDate.Text = aprRecDate.ToString("dd/MM/yyyy");
    }
}

Posted 8-Jun-12 0:15am

Robymon

Add a Solution

3 solutions

Solution 1

Use DateTime.ParseExact[^].

SQL

this.Text="30/12/2012";
DateTime date = DateTime.ParseExact(this.Text, "dd/MM/yyyy", null);

Posted 8-Jun-12 0:19am

codeBegin

Comments

Robymon 8-Jun-12 6:36am

I tried this also, but still showing the same error

Solution 4

hi,

Convert.ToDateTime(objDateTime);

Posted 8-Jun-12 4:35am

Member 7673223

Comments

Maciej Los 8-Jun-12 10:59am

Bad answer. Try to convert string "9-5-2012" to date. Read about Convert.ToDateTime(objDateTime) - Remarks section.
If you prefer not to handle an exception if the conversion fails, you can call the DateTime.TryParse method instead. It returns a Boolean value that indicates whether the conversion succeeded or failed.

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)

VJ Reddy · Accepted Answer · 2012-06-08T03:49:00

The reason is that by default the DateTimeFormat of the CurrentCulture is used in parsing the date.

In your local machine the DateTimeFormat of the CurrentCulture may be in the dd/MM/yyyy format hence there may not be error.

Whereas on the webserver the DateTimeFormat of the CurrentCulture may be MM/dd/yyyy and since 30 is more than maximum month value the above error may be thrown.

So, when using DateTime.ParseExact the InvariantCulture can be used to avoid this problem as shown below:

C#

DateTime date = DateTime.ParseExact("30/12/2012","d/M/yyyy",
    			System.Globalization.CultureInfo.InvariantCulture);

The d/M/yyyy format matches the date and month both in single digit and double digit like 09/05/2012 and 9/5/2012 whereas the dd/MM/yyyy format requires both the date and month to be in exactly two digits. Otherwise it will throw error. So, 09/05/2012 can be read by it, but for 9/5/2012 it will throw error.

Hence, it is preferable to use d/M/yyyy format.