Date Format - best way of converting a string into a date format

[Brian Candy]

I am guessing that this must be a common question, but I just can't
find a simple solution for it by searching the newsgroups. I have a
Text Box with a date in a UK format. The format has been verified and
is legal. Now all I want to do is pop it into an SQL field. Debugging
on my local machine everything works with the following:

dDOB = CDate(txtDOB)
Row.Item("DOB") = dDOB

But when deployed this would fail because CDate requires MM/DD/YYYY
rather than DD/MM/YYYY.

In short I want to display and collect dates from users with the date
format DD/MM/YYYY which is fine on my local machine, but not on my
server farm. If I use string manipulation to solve this, it works on
my server farm but not on my local machine. I could write some
un-elegant code to solve this, but I am convinced there must be a
simple way of overcoming this problem.

Thanks in advance for any help.

Brian Candy

[Martin Dechev]

Hi, Brian Candy,

You can try the static method ParseExact on the System.DateTime structure:

http://msdn.microsoft.com/library/en...ExactTopic.asp

And then pass the DateTime value as a parameter to insert it into the DB.

Greetings
Martin
"Brian Candy" <br***@01792.com> wrote in message
news:ja********************************@4ax.com...

I am guessing that this must be a common question, but I just can't
find a simple solution for it by searching the newsgroups. I have a
Text Box with a date in a UK format. The format has been verified and
is legal. Now all I want to do is pop it into an SQL field. Debugging
on my local machine everything works with the following:

dDOB = CDate(txtDOB)
Row.Item("DOB") = dDOB

But when deployed this would fail because CDate requires MM/DD/YYYY
rather than DD/MM/YYYY.

In short I want to display and collect dates from users with the date
format DD/MM/YYYY which is fine on my local machine, but not on my
server farm. If I use string manipulation to solve this, it works on
my server farm but not on my local machine. I could write some
un-elegant code to solve this, but I am convinced there must be a
simple way of overcoming this problem.

Thanks in advance for any help.

Brian Candy

[Janaka]

Hey Brian,

Sounds like your web server farm is set up using US settings. You can set
the localisation to uk formatting by doing one of two things:

1) Setting the locale identifier in the page directive: <%@ Page
LCID="2057" Language="VB" %>
2057 is the locale for UK. This will work on the page in question.

2) Setting the culture for the entire site. This has to be done in
web.config by applying the following tag within <system.web>
<globalization culture="en-GB" uiCulture="en" ></globalization>

Hope that helps.

Janaka

"Brian Candy" <br***@01792.com> wrote in message
news:ja********************************@4ax.com...

I am guessing that this must be a common question, but I just can't
find a simple solution for it by searching the newsgroups. I have a
Text Box with a date in a UK format. The format has been verified and
is legal. Now all I want to do is pop it into an SQL field. Debugging
on my local machine everything works with the following:

dDOB = CDate(txtDOB)
Row.Item("DOB") = dDOB

But when deployed this would fail because CDate requires MM/DD/YYYY
rather than DD/MM/YYYY.

In short I want to display and collect dates from users with the date
format DD/MM/YYYY which is fine on my local machine, but not on my
server farm. If I use string manipulation to solve this, it works on
my server farm but not on my local machine. I could write some
un-elegant code to solve this, but I am convinced there must be a
simple way of overcoming this problem.

Thanks in advance for any help.

Brian Candy