Re: Sanity check

[Chris Rehm <javadisciple@xxxxxxxxxxxxx>]

I'm confused, Lois. Are you familiar with this application? Maybe I just
missed the post that mentioned this indicator is in use nowhere else.
I'm sorry if I missed the post that said the code had been checked to
assure the indicator wasn't in use elsewhere (of course, including
screen activation). I realize that I haven't been following this thread
that closely.

But often the reason for setting on indicators is to condition some
later event. The code snippet we see seems to determine that the record
being processed is a memo (credit or debit) rather than a purchase
order. Different events and outputs might be necessary based on that and
it wouldn't be unusual to use an indicator to trigger the different events.

Personally, I'd hesitate to chop out the use of an indicator without
being able to look at the rest of the program.

Lois Krake wrote:

>David
>
>You are correct in your analysis of this. I maintain thousands of lines of
>code like this every day. Indicator 44 is only used to control whether the
>if statement executes and it only executes if cm = 'CM' or 'DM'. Jon's
>rewrite definitely made it more legible.
>
>Lois
>
--
Chris Rehm
javadisciple@earthlink.net

Beloved, let us love one another: for love is of God; and every one
that loveth is born of God, and knoweth God. 1 John 4:7