It always worked this way. Don't feel bad, I found about it only a few years ago. :)

>Has it always been that a string comparision works differently in SQL than FoxPro? or was that just with VFP8?
>
>And yes, there is no reason for the alltrim and upper - just habit because the alltrim and upper byte me so many times - as does the == and now the SET ANSI.
>
>>A string comparison works differently in SQL commands and in the rest of FoxPro. See SET EXACT and SET ANSI for details. With both those settings OFF, "" <> "04" is true in the command window and false in the query. It's better to avoid ALLTRIM() function in the queries WHERE clause. I don't see >why do you need ALLTRIM() and UPPER() in this case at all.
>