Weird Date Formatting

[jfrost10]

Hey all,

I have a date that I need to stick into Oracle. If...

Regional Settings = MM/dd/yyyy
and
Format in code = MM/dd/yyyy
this will go through no problem.

Regional Settings = dd/MM/yyyy
and
Format in code = MM/dd/yyyy
this will error out at the Oracle level

Regional Settings = dd/MM/yyyy
and
Format within vb.net code to MM/dd/yyyy
this will error when I try to assign the formatted value to a date or a datetime variable.

Does this make any sense? I mean, if we format the date a certain way, shouldn't the date/datetime variable be able to be assigned to it even though its different from the environment settings?

Thanks,

D

 

[chmohan]

Depends on how your code reads it have you used Format Function for this?

 

[jfrost10]

Yes.

 

[chmohan]

is the error at the ui or db level?

 

[chmohan]

see the Accepted Answer (down below in the page when you open the link)in this link

http://www.experts-exchange.com/Programming/Programming_Languages/Dot_Net/VB_DOT_NET/Q_21041085.html

 

[jfrost10]

Ah, the issue for us seems to be that the Date variable apparantly must be in the M/d/yyyy format and you can't shove a dd/MM/yyyy formatted string into a date variable.

D

 

[chrissie1]

are you using parameters??



Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[chiph]

If you use a modified ISO-8601 format (yyyy-mm-dd hh:mm:ss.ssss) you'll seldom have problems with your database recognizing the format.

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first