>>>Technically, I guess you are right
>>
>>Why the restriction?
>
>I think for the result of the query, if you assign a value first to the 'parameter', it makes no difference whether you use parameter or ?parameter
>
>But I always use the ?
>
>- It's clearer
>- I use this ? to find the parameters in the SelectCmd of my cursoradapterclass and map those to properties of the class
>I can then use
>

>=  caObj.SetParameter('MyParam', 27)
> = caObj.CursorRefresh()
>

>
>>Just kidding.

Never thought that as a markup, not realy valid in SELECT part. While it works it might break with next version. (That was at VFP 5.0)

I always code like

SELECT Cur1.xField FROM cursor AS Cur1 WHER Cur1.xField=xxVar

#1 Hungariaon notation, a field (xX) looks not like a variable (xxX)
#2 A variable has no alias. (object.property will not work in SELECT SQL)


I always use (SQL) alias. I had two times a quarrel with unclear fields - never more. And early multiple dabasese etc, so if I adress a table it is

SELECT Cur1.xField FROM dbc!table AS Cur1 WHER Cur1.xField=xxVar

no exception

:)