
March 1st, 2003, 09:39 PM
|
|
Contributing User
|
|
Join Date: Feb 2003
Location: St. Louis, MO USA
Posts: 43
Time spent in forums: < 1 sec
Reputation Power: 11
|
|
|
you could always detect your 80% locales and provide a parse function depending on the locale, assuring that the date is properly formatted before entering your code.
But from personal experience, I have found that usually problems like these are best kept out of back end code, and solved by very very rigid user input code and clear instructions. If this is NOT a user interface input method for your date value, then I would analyze your data and rule out certain "out there" circumstances, and only code for the crazy stuff when and if it occurs. This may sound lazy, but as I am paid hourly as a freelance consultant, I just inform the client of my decision and they are usually thankful to save the money up front.
__________________
- Chris of Custom Fit Technology
http://www.customfittech.com
Access to MySQL Conversion Tool,
Visual XSLT Conversion Tool
|