Dr. R>
>IF v1 <> 'This' THEN
>-- will not be a hit (it used to be before the fix in 6.5++)
>ENDIF
>Before this fix in 6.5++, the comparison "IF v1 <> 'This'
>THEN" would be a hit with EQNULL set ON or FALSE when it
>should only be a hit when EQNULL is ON. This means that
>now "IF (.v1) <> 'This' THEN" and "IF v1 <> 'This' THEN"
>will both process the same way. In the past they would
>be different because of this problem.
I'm not real sure I like this 'fix'. Maybe you're right in
saying that's how it SHOULD have always worked, but programs
written in previous versions of RBase relied on it being a hit
when EQNULL is OFF (which it is in all my applications except
for setting it temporarily ON when it is needed). If I upgrade
a client to 6.5++ and want to make sure I don't break code, I
would have to go thru every IF statement to see if I need to
change it in case of a null comparison. I don't see any
easy way of doing this. I cannot fix it by SET EQNULL ON without
making sure I don't break code somewhere else when comparing
a null to a null!
Karen
