>The second is even less related to SQL but more to my personal style of coding and xBase/vfp behaviour: in xBase the table field to be changed can be coded as a name expression

>replace all ;
>     (loFldVar.Plz) with "60435";
>   , (loFldvar.Street) with "Koselstrasse 18A";
>   in (lcmyTable)
>
>as well as Macroexpansion
>
>replace all &lcPlz with "60435", &lcStreet with "Koselstrasse 18A"
>
>whereas the update - SQL works only as Macroexpansion:
>
>Update (lcmyTable) ;
>   Set &lcPlz    = "60435";
>     , &lcStreet = "Koselstrasse 18A"

>
>Probably I should switch over to building the whole SQL command either in code or via Textmerge, but some habits are "just there". This often comes up when reformulating some fieldmapping code from xBase-code to SQL: espeially when the xBase already uses objects via for code clarity it nags me hard enough to test again<g>. But OTOH name expression works with "store" only and not the typical "myTarget = mySource"...

I'd change to using TEXT ENDTEXT. You know 15 or 20 macro expansions is slower than 1.