I'm not sure I understand your point now. Are you contending that there is a flaw in the information I provided in this thread? If so, what would be the part that you are taking issue with as it relates to the original poster's problem? As you and I both know, the SET ANSI setting has nothing to do with whether...

?'Domestic Chassis LED' = 'Domestic Chassis'

...returns .T. or not, and in the same way it has nothing to do with the comparisons that the original poster is doing in the DO CASE statement. While, the SET EXACT setting does effect the return value, which is precisely why I used it. Furthermore, while SET ANSI does not override the SET EXACT setting for the code given, "==" does in fact override it, which is why I presented "==" as well. If I am missing something here, or you believe me to be in error, please correct me.

>>>Craig, Pardon me,
>>>for completeness:
>>>SET ANSI ON is equal to "=="
>>>but
>>>SET EXACT ON is not eqaul to "=="
>>
>>Hi Fabio,
>>
>>Yes, you are technically correct. However, Torrey is not using any SQL Commands in the example of the problem. So, I felt that Set Exact On was appropriate. It is definitely important that Visual FoxPro developers understand the difference between Set Exact On and Set Ansi on... I appreciate you bringing this into the discussion.
>
>I write this because you put "==" into the discussion.
>
>Here the VFP shows the best of it:
>

>* SET EXACT is XBASE setting
>* SET ANSI  is SQL setting
>
>* relation
>"SQL =="        is equal to "SET ANSI ON"
>"SET ANSI ON"   is equal to "SET EXACT ON"
>
>Then "SET EXACT ON" is equal to "SQL =="
>but  "SET EXACT ON" is not equal to "XBASE =="
>

>
>I would have preferred:
>

>=   SET  OFF = short match
>==  SET  ON  = without trailing blank match
>===            fully match
>