>VFP treats '&&' as begining of inline comment regardless if it's inside string literal or not. IMO, it's a bug which not going to be be fixed.
>You'll have to either split string literal or replace '&' with CHR(38)
>

>UPPER(Password)="&" + "&ETC       "
>* or
>UPPER(Password)= CHR(38) + CHR(38) + "ETC       "
>

What is sad about this is that it means wherever we have such a search where the data comes from a table or from something the user entered, we would have to do a STRTRAN() in order to make sure it will always work. Assuming the user would enter something like that, it would fail.

However, when doing the same SQL, by the use of VFPOleDB, from the .NET environment, as I always use a parameterized approach, this should not happen.