|
Someone noticing 1,000,001 items on an otherwise valid order, is what brought all this up in the first place. I guess it takes something like this to get everyone's attention. #1 is what we are doing also, in this particular instance, but #2 is out of my jurisdiction (beauracracy and all, you know), but I will look into the possibilities of doing such a thing (if I can even find out whose jurisdiction it is). Of course, they will just say that their job is to make sales, not to worry about data entry errors. That's what they hire us propeller heads for. If they make errors, we're supposed to catch'em. And, I suppose in the long run, they're right. They are profit centers, we are overhead. Thanks, Buck. > -----Original Message----- > From: Buck Calabro [SMTP:Buck.Calabro@commsoft.net] > Sent: Wednesday, April 10, 2002 5:14 PM > To: rpg400-l@midrange.com > Subject: RE: Keyword on DSPF entry field > > Nelson wrote [regarding sanity checking all inputs]: > > >In a perfect world, I certainly agree with you. > >I've just never seen such an application in > >real life. I suppose if you were a vendor > >that had the luxury of constantly working on > >and improving the same application over and > >over, for years on end.........sigh > > I hear you about retrofitting. Very loud and very clear. What has > happened > to me personally is that when I get 'one of those' screens where people > make > lots of mistakes, I add the edit checking. It's an incremental process > rather than a complete re-do. Training people to use the keyboard > properly > isn't really an unreasonable expectation. After all, somebody explained > how > to sign on, press Error Reset, etc. Line people have managers, and if the > data suggest that Mr Oopsie makes more than his fair share of data entry > mistakes, then Mr Oopsie's manager should take a moment to find out why. > > This is one place I actually made some points in a prior job. When an > anxious warehouse manager called me to find out 'what idiot ordered 100000 > cases of toilet paper' it was a bit of work to track down the offending > order, but two good things came of it: > > 1) We put an 'are you sure?' window in the entry program > 2) We found that we were putting employees > in the field without proper training, so > we updated our 'when we hire people do this' > list > > It isn't hopeless at all! > > --buck > > "This box Rocks!" - related to 2002 NE IBM > Conference attendees by IBM's Stephanie Joy > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. ************************************************************************************************************************************************************************************************************ This message originates from Lincare Holdings Inc. It contains information which maybe confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. ************************************************************************************************************************************************************************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.