Kooray, I do agree with Rick in a way. It is the same as decimal fields.. It is like if you leave the Submitter field open for editing, you could enter any free text and it would take it - there is no check to verify if it is really a valid login name that exists in the User form. Realistically that is what you need to put in field 2. Or for e.g. entering j...@dsouza@yahoo#com in an email address field.. It will accept it unless you build customized error checks for it..
And if you are really that worried, well make a project of it - copy the contents of all editable date fields in temp fields during your modify or save transactions into a character field and check for the presence two slashes.. If not found reject the input. Or change the format of short date to long and check for the presence of appropriate date related strings in the right places.. In your defense however, yes it would be nice if a date field was more like how a date field in Outlook Calendar field was where the field has distinct placeholders within the field for day month and year which would not allow invalid input within each place holder.. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]]on Behalf Of Rick Cook Sent: Thursday, June 24, 2010 3:21 AM To: [email protected] Subject: Re: Date/Time Field - Bug Found "Doctor! Doctor! It hurts when I do this!" "Well, then don't do that!" I would suggest that if your users did any number of incorrect things, they would get results they didn't like. This is not a bug, it is a PEBCAK issue. Train your users in the correct format for the Date/Time string, and their results should improve accordingly. ------Original Message------ From: koray Sender: Arslist To: Arslist ReplyTo: Arslist Subject: Date/Time Field - Bug Found Sent: Jun 24, 2010 3:10 AM Hello all, My regional settings for date/time field is as follows: 6/24/2010 9:45:12 AM If I (or the user) enters date/time as "24062010 9:45:12" remedy creates the database entry with integer value of 24062010 - which maps to actually "10/6/1970 2:53:30 PM". Therefore this causes a big unstability and I guess another bug of Remedy ARS. BR, Koray _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
