At 03:26 PM 1/17/01 +0000, you wrote:
>Apologies if this has already been covered. I'm having a general problem
>with date formats, specifically if a form field is submitted with a 2-digit
>year then the subsequent template receives it with the day and year digits
>switched round.
>
>ie 17/01/01 would become 01/01/2017
>
>This doesn't happen if the form field contains a 4-digit year ie 17/01/2001,
>but as I'm using cfinput validation it doesn't actually force the user to
>use 4 digits. At present I don't know whether this is a localised setting
>issue or if it's cold fusion or what. Anyone else come across this?
I haven't come across this but I do see an issue in your example that might
cause it. The first part of a date (in US format which is the default) is
the month and there is no 17th month. Perhaps CF server recognizes that 17
is not a month and decides that it must be a year instead.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
