>Is this still true?
>
>oldvalue = ""
>value = "anystring"
>
>oldvalue = value (returns .T.)
>
>I thought this problem was fixed long ago, but I just ran across a situation where it appears the problem was not fixed.
>
>I SET EXACT ON still the cure?
>
>regards,

It's always considered as a feature (not bug) and SET EXACT (SET ANSI for Select-SQL) should still care about it.