Normal Topic Date field issue (Read 751 times)
Bob_Hansen
Senior Member
Members
*****
Offline


WOW, They have the Internet
on computers now!

Posts: 1861
Location: Salem, NH
Joined: Nov 24th, 2002
Date field issue
Jan 5th, 2004 at 12:30am
Print Post Print Post  
Going through the Tutorial.  Adding records to Contacts Form. 

Intentionally added bad date (US): 13/01/2004.  Record gave no warning that it was bad, made auto change to 01/13/2004. 

Added bad date 13/25/2004, record was saved, date field is empty, no warning.  More bad dates are rejected with no warning, just leave a blank date field. 

See same issue with Call Details, Time of Call field.  If bad value, record is saved with blank value, no warning.

I think that there should be a warning if the format is not a valid date.  This type of error should not require programming to validate.  It should not make a change by itself, and it should not make a blank.  Many typists never look at the screen, and they will not see that the date/time field has been cleared/changed.  Best option would be send alarm when doing exit on field vs. when closing record, since other programming might be a function of this value.
  



Bob Hansen
Sesame Database Manager Professional
Sensible Solutions Inc.
Salem, NH
603-898-8223
Skype ID = sensiblesolutions
Back to top
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Date field issue
Reply #1 - Jan 5th, 2004 at 2:50pm
Print Post Print Post  
Sesame, accepts 25 different date formats as input. In about half of those 13/01/2004 is a perfectly legal date. The output format, nor your system output setttings determine the legality of a date. The application programmer *must*, if they need to have a layout element non-blank, check in code based on their own criteria. We do not try to enforce any particular criteria on your application - in that that would interfere with the application programmer from making that decision. This is especially vital for applications being deployed on international networks, where the application programmer may want us using the system settings on the server as opposed to the client, or vice-versa.

We do check your (client) system setting to determine a "leaning" - if you enter a nebulous date (legal by both MM/DD/YYYY and DD/MM/YYY) we lean toward your system settings.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged