No, that's the weird thing...I had this requirement specifically when people where typing into the field, they just sometimes fat finger things and put special characters into the numeric fields and wanted me to throw errors when it happened. And, the weirdest thing is that the system throws NO errors when you do it, it simply considers the input invalid and truncates at the invalid error, so if you entered 123$5, everything past the $ gets truncated and your actual value in the field is 123.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of David Durling Sent: Wednesday, November 07, 2012 8:56 AM To: [email protected] Subject: Re: Real Number Format Issue Okay, thanks, I don't know if I've ever tried that - but then this must be for situations where someone's not directly typing into the real field, or they'd get the system-generated error, correct? David > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Longwing, LJ CTR MDA/IC > Sent: Wednesday, November 07, 2012 10:46 AM > To: [email protected] > Subject: Re: Real Number Format Issue > > David, > The problem is that if you have a run-if firing on a qual of something > similar to > > 'Real Field' LIKE "%&%" > > And throw an error if true, you will find that the filter never fires > because the real field will actually truncate the data at the & before > it even hits the workflow. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of David Durling > Sent: Wednesday, November 07, 2012 8:16 AM > To: [email protected] > Subject: Re: Real Number Format Issue > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Allan See > > Sent: Tuesday, November 06, 2012 8:35 PM > > To: [email protected] > > Subject: Re: Real Number Format Issue > > > > Thank you for all the reply, > > > ... > > > > @David - there has been a couple of instances that users input > > special characters accidentally, and these values do not get > > filtered causing process to stop. i dont believe it is a process of export > > from databases. > > Alan, > > Sorry, guess I still don't understand, but at least Misi & LJ do. I > get "You have entered an improperly formatted value for a real field" > when I try to save with 123.2&5 in a real number field in the User Tool or > web. > > But rather than try to change the input, how about throwing an error > to the user telling them to correct it? Or does that have the same > problem with being unable to detect the incorrect characters on input? > > David > > David Durling > University of Georgia > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
