But you can accept that value just fine -- it's a date. <cfset d = "July 26, 2005"> <cfset newd = dateFormat(d, "mm/dd/yyyy")>
yields: 07/26/2005 So you have no problems here. As long as you're checking for validity, you're good to go. Now you only have to worry about handling the instances where some knucklehead puts 03.07.2005 in the field expecting it to yield July 7th instead of March 7th., but you've got to draw the line somewhere, right? --Ferg. Les Mizzell wrote: >>Just force them to enter a date correctly. >> >> > >I wanted to go with three dropdown boxes for month/day/year, but was >told "nope, just one text input". > >So, next to the text input in bold red letters, it says: >(format date as mm/dd/yyyy) > >In previewing the thing to the client, they started filling out the form >and immediately entered "July 26, 2005" and ignored the format alert. > >It's often amazing to me the weird "stupid user tricks" that you have to >compensate for - and if you haven't thought of it yet, the user >certainly will within 24 hours of getting a finished product! > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211322 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
