>>Hi Brad,
>>
>>Not exactly. The field2 itself is incorrect in result also, Null instead of blank.
>
>That's true about the NULL's... that shouldn't be happening at all. But it's the EMPTY() function in the WHERE clause (or more correctly the NOT EMPTY()) that seems to be driving this not to work.
>
>Doing a WHERE taba.field2<>" " is the same as doing a WHERE NOT EMPTY(taba.field2) yet one returns the correct result and the other doesn't.
>
>I tried the same by changing field2 to a numeric field and date other types of fields and the same phenomenon happens. If you get rid of the NOT EMPTY() in the WHERE clause, everything works as expected.
>
>Weird.
>
Brad,

? NOT EMPTY(Null)    && .T.