Thanks Sergey

This is the first time I came across this. I was not aware that it existed way back to Fox 2.6.

Simon


>Hi Simon,
>
>It's a known issue since FOX 2.6 days, maybe even eirlier. FoxPro incorrectly treat '&&' in the string literal as beginning of the inline comment. A workaround is to separeate '&&' characters.

lcTxt= "&" + "&"
>lcTxt = "!!!#&" + "&"
>and so on
>

>
>>Hi
>>
>>If you try any of the following you get an error in VFP 7 and VFP8.
>>
>>lcTxt="&&"
>>
>>lcTxt="!!!!&&"
>>
>>lcTxt="!!!#&&"
>>
>>Store "&&" To lcTxt
>>
>>However, the following works okay.
>>
>>lcTxt="&"+Chr(Asc("&"))
>>
>>
>>You maybe wondering why I am interested in this problem. The problem arose when analyzing some data with unique ID values that occassionally ended in the double "&" sign. I received and error any time I tried to store the ID value to a memory variable or use the Set Key To (lcID) when ID or lcID ended in the double "&" sign.
>>
>>Thanks,
>>Simon