>>The print when in a report field said
>>

>> bill_type <> "ST"
>>

>>All was well till some rows with bill_type = "STRAP" disappeared and the user complained.
>>Yes, I know that's how VFP works, but it's a PITA.
>
>Bill,
>
>We reverted all of our string2 <> string2 to !string1 == string2. Nowadays, we are only observing the <> in our projects in 3rd-party libraries, but most of the time it's a test against VARTYPE() or TYPE() results, so there is no problem witch exactness.

Reminds me of the old joke

If A = B and B = A and (not (A <> B) ) and ( not B <> > A)