>>Try this

TEXT to mSqlcommand noshow pretext 15 TEXTMERGE
>>UPDATE MyView
>>	SET
>>		Field1 = nValue1, 
>>		Field2 = <<.nSomeValueIHave>> 
>>	WHERE code = nValue3
>>ENDTEXT
>>&mSqlCommand

>>
>>Be sure to remove all semicolons in your code. The TEXTMERGE comment will replace

<<.nSomeValueIHave>>

with the value of your form property.
>>HTH
>
>
>Bad idea. SQL injection risk
>
>Relevant:
>http://xkcd.com/327/

I just realized you are using this in a view. I only use this in PRGs working on local cursors and the code is compiled into an EXE. In that case there can be no risk.