>I always use a method of entering the date that is understandable to all
>(world wide). The method is to offer a field for day an option button for
>written month and a field for year. This way there is no confustion and you
>can give it a professional look.
If you are working with current dates (less than 12 months past) there is a
more fool-proof approach that works well for me: display the current
month's calendar (with buttons for next/previous month) and have the user
click on the desired date. Using this approach there is no need for date
validation because it is impossible to enter an invalid date, whereas your
approach requires validation (eg: day > last day of month, Feb 29 in a non
leap year, etc.).
>IMHO expecting the user to adhere to a your
>date format is never going to look professional.
Take a closer look at this statement in conjunction with the one above...it
is you who expects the user to adhere to your format, even if she/he has
indicated a different preference in the Control Panel. What Jeanne and I
are suggesting is that the date format should adhere to the user's
preferences rather than the user adhering to the programmer's date format.
Rob Cozens
http://www.serendipitysoftware.com/who.html
"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631)
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
