Tolerance for entry mistakes brings up another possible approach: select menus for everything except year.
That would solve all of these problems. We can just replace all those entry fields (except the year) with select menus, and JavaScript can modify the contents of the Day field so that only that number of days appears for the month chosen. February would automatically adjust for leap years. How about this approach, folks? Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive Training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now! ----- Original Message ----- From: "Angel Stewart" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, August 16, 2004 10:54 AM Subject: RE: [plum] DisplaySearchDateTimeControl not working > Hey Adamn, > > This sounds good to me. > > I saw a time field recently that allowed someone to enter : 1pm and it would > convert that to a proper 1:00 pm time value. > Or 815a would become 8:15 AM in the time field of the database. 1222am would be > 22 minutes past midnight etc. > > I haven't yet installed this Plum Beta version, but if the field doesn't work > this way > I think this would be a neat alternate way for time entry. > > -Gel > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Adam Churvis > > 1) We pre-populate the day field with the word "day", the year field with the > word "year", and the time field with the word "time". > >
