I have written a custom tag that will solve your problem. You call the tag
and it gives you 3 drop down list boxes already filled with the month day
and date fields. You can display the boxes in the order you chose via passed
params. You can also set the way the contents of the boxes are displayed,
using the DateFormat() standard masks. The niftiest part is when you change
the month box, the day box automaticly repopulates itself with the maximum
number of days in that particular month .. except for Feb. which displays 29
days (dang leap year .. I'm still working on that ;) It has a bunch of
other features, but they aren't important in solving your problem.
The tag isn't up on Allaire's DevEx yet (awaiting approval), but I can
e-mail it to you if you are interested.
Contact me off list at [EMAIL PROTECTED]
Todd
----- Original Message -----
From: "Katrina Chapman" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, January 17, 2001 6:26 AM
Subject: RE: Date problem
> Since you're using European dates I would suggest breaking up the date
> field.
>
> IE:
>
> <!-- form page -->
> ....
> <input type="text" name="dayofmonth"><input type="text"
name="month"><input
> type="text" name="year">
> ....
> <!-- end form page -->
>
> <!-- submit page -->
> ....
> <cfset final_date = month & "/" & dayofmonth & "/" & year>
> ....
> <!-- end submit page -->
>
> Then you can reformat it for output to the screen at a later time.
>
> If you do it this way you won't have to worry about what order the people
> enter the data because it will always be the same.
>
> --K
>
> -----Original Message-----
> From: Neil Robinson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 17, 2001 3:26 PM
> To: CF-Talk
> Subject: Date problem
>
>
>
> 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?
>
> TIA
>
> Neil Robinson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
