Why is this debugger line TRUE?

[Kenneth Brody]

On 12/15/2011 1:54 AM, Stanley - stanlyn-com wrote:
> Top post...
>
> In this case, the if statement should be false, but it is showing true.

Because it _is_ true.

> This code is being triggered when saving the record that calls the
> subroutine.  This subroutine is also called by a @wlfI7) routine at other
> times.
>
> Lets dissect it...  The I2) component by itself is true, and the I7)
> component is false...  Just look at the I7) part of the if statement that is
> If: I7) eq "", and then look at the last line where I asked the debugger
> "what is the value of I7)?" and it shows me its 18.70 also shown on the last
> line, so clearly the reported value of 18.70 is not equal "" as shown in the
> if statement, and that why it should be evaluating to false...
>
> Is the debugger trustworthy, as it sure has it wrong here, or am I missing
> something?

Yes, you are missing all of the replies which have already explained this 
situation to you.

When in "regular" input processing (which is the case here, as you say 
"triggered when saving the record", as opposed to the other time when it's 
executed in the @WLFI7 event handler), the test for

     If:  I7) eq ""

will be true if _any_ of the instances of I7 is blank.  Please use the 
debugger to check every instance of I7 individually, and you will see at 
least one that is blank.

[...]

-- 
Kenneth Brody