Re: Was a decimal point keyed?

I included some "reasonableness" checks in the code and they are working properly. They definitely help but only to a point. I still had a user manage to sneak through a price of $0.0015, when they really wanted $15.0000. Unfortunately we have a wide range of prices, from well over $200 to somewhere around $0.0004. The "reasonableness" target becomes somewhat elusive.



"Jerry Adams" <Jerry@xxxxxxxxxxxxxxx> wrote in message news:mailman.38578.1279038469.2580.midrange-l@xxxxxxxxxxxxxxx
Our users, too, came off the /36 and most of the order entry programs are still RPG II.

I built a "native" promotions (reduction from the selling price) table and maintenance program which hooked into the order entry. One of the users keyed "150" (sans decimal point) when she wanted a promotion of $1.50. Needless to say we were giving some hefty deductions that day until someone actually looked at one of the invoices.

We are going to be a mixed shop (II and IV) for a long time, but that's the only time I recall any user getting confused on the issue. Space permitting on the panel, I always add a note such as, "(2 decimals)". I'm not about to jump through extraneous hoops because they have issues (which, as I said, doesn't seem to be the case), but I did add a reasonableness check in the above maintenance program: "Really? Wow!" if the promotion is outside a mathematical range (more than 10% of the basic selling price).

Jerry C. Adams
IBM System i Programmer/Analyst

It just as easily could have gone the other way. - Don Zimmer explaining his team's 4-4 road record