Re: OPNQRYF - Sort by a calculated field

[Dan <dbcemid@xxxxxxxxx>]

Great to hear, Peter!  I understand that you cannot allow "unexpected"
results to print on your report, but you should be able to trap those
out-of-range calculated values in the RPG program and decide what to do
with them there.

If you are interested in pursuing this further, what are the numeric
attributes of the three fields OBSTKVAL, OSTKVAL, and OQTYW1?  This
will help determine whether my idea will work.  Hint: The bigger, in
terms of significant digits, that OQTYW1 is, the better a chance that
this will work.

HTH, Dan

--- Peter Vidal <Peter_Vidal@pall.com> wrote:
>
> "Just for future reference, the error message you're getting on this
> is
> treating "OBSTKVAL/OSTKVAL" as a qualified field name, i.e., field
> OSTKVAL in record format (file???) OBSTKVAL.  See what happens if you
> use a space before and after the '/'."
>
> I tried it and... you were correct Dan!  Thank you!
>
> For my "common" field OQTYW1, I left the mapped field type blank,
> which defaults
> to *CALC but the spaces before and after the operation designator
> really was the
> fix to execute the division correctly; however, I have to work with
> the fact
> that I WILL HAVE the "division by zero" scenario on many cases.
> Specifically on
> this report (and based on you recommendations) I cannot allow any
> "unexpected"
> results as expected, specially if you are trying to determine
> inventory
> obsolescence, which is the report's purpose.
>
> Thank you Dan for your advice on this.  I have learned a new thing
> today!
> Feels good!
> Peter Vidal
> Pall Aeropower Corp. / SR Programmer Analyst
> www.pall.com  /  Peter_Vidal@Pall.com
> 727-539-8448, x2414

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com