Since CF defines a date so loosely, I'm thinking that I just really need to create my own definition per application and run those checks. In the scenario above, I just checked for a year range of 1900-3000 (pretty big range, I know...), which was fine since I was only trying to figure out if the value was a date for display purposes.
As Aaron has done, I normally try to have a solid client interface with isDate validating on the backend. I can see that a simple UDF may be in order for a little more advanced date validation.. Mike also brings up a good point about the database failing on a date that passes isDate validation. I guess it all just depends on the app requirements and how bullet-proof it needs to be... >One thing you can do is simply validate the date range. What dates are >acceptable? A combination of isDate() and dateCompare() will do that for >you... > >On Jan 24, 2008 2:05 AM, Mike Chabot <[EMAIL PROTECTED]> wrote: > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:297287 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
