By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,086 Members | 1,450 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,086 IT Pros & Developers. It's quick & easy.

Convert Date pb

P: n/a
Hi,
'm gettin mad about date conversion.
Here is the point.
Got and add-in for Excel which call functions from a web service (on a
remote server)
The remote server has regional settings set to "en-UK" and date to
dd/MM/yyyy. (I'can't change it !)
One of my function get a string as parameter and convert it to date in
the following format yyyy-mm-dd.
So, Having regional settings set to "fr-ch" (date format dd.mm.yyyy), I

call my function with "31/10/2003"... Works grate (with every date).
Changing regional settings to "en-US" and date to default "M/d/yyyy",
the function do not recognize the date.
I tried to set CurrentThread culture to a specific one, I tried
Date.Parse... I must miss somethin...
Is there a way to get back client date format during request and
convert the string date he filled to yyyy-mm-dd regarding this format ?

Help Please !

Nov 17 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Franck" <we**********@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
Hi,
'm gettin mad about date conversion.
Here is the point.
Got and add-in for Excel which call functions from a web service (on a
remote server)
The remote server has regional settings set to "en-UK" and date to
dd/MM/yyyy. (I'can't change it !)
One of my function get a string as parameter and convert it to date in
the following format yyyy-mm-dd.
So, Having regional settings set to "fr-ch" (date format dd.mm.yyyy), I

call my function with "31/10/2003"... Works grate (with every date).
Changing regional settings to "en-US" and date to default "M/d/yyyy",
the function do not recognize the date.
I tried to set CurrentThread culture to a specific one, I tried
Date.Parse... I must miss somethin...
Is there a way to get back client date format during request and
convert the string date he filled to yyyy-mm-dd regarding this format ?

Help Please !


Given a date, you can try DateTime.Parse to return a date...

Let us know how it goes! :)

Mythran

Nov 17 '05 #2

P: n/a
The point is that I can figure out how the user filled the date...
All case worked with a Convert.ToDateTime.

31/12/2005 -> OK
31/12/05 -> OK
12/31/2005 -> OK
12/31/05 -> OK
BUT, when the user send an "ambiguous" date (5/1/2005 could be 5th of
Jan or 1st of May regarding regional date settings) here is
nightmare... If the user is in M/d/yyyy, the Convert.ToDateTime
convert in dd/MM/yyyy

SO, I'm trying to know user's date regional settings in order to make
the correct Date.Parse.

Help :(

"Mythran" <ki********@hotmail.comREMOVETRAIL> wrote in message news:<eJ*************@TK2MSFTNGP15.phx.gbl>...
"Franck" <we**********@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
Hi,
'm gettin mad about date conversion.
Here is the point.
Got and add-in for Excel which call functions from a web service (on a
remote server)
The remote server has regional settings set to "en-UK" and date to
dd/MM/yyyy. (I'can't change it !)
One of my function get a string as parameter and convert it to date in
the following format yyyy-mm-dd.
So, Having regional settings set to "fr-ch" (date format dd.mm.yyyy), I

call my function with "31/10/2003"... Works grate (with every date).
Changing regional settings to "en-US" and date to default "M/d/yyyy",
the function do not recognize the date.
I tried to set CurrentThread culture to a specific one, I tried
Date.Parse... I must miss somethin...
Is there a way to get back client date format during request and
convert the string date he filled to yyyy-mm-dd regarding this format ?

Help Please !


Given a date, you can try DateTime.Parse to return a date...

Let us know how it goes! :)

Mythran

Nov 17 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.