>>Gregory provided you with the correct way of using parameters. One possible gotcha - check out the types of the parameters, quite often VFP sends them wrongly (say, float for numeric, etc.) In those cases you can use CAST to correct type inside the ?mproperty, e.g.
>>
>>'cast(?mProperty as NUMERIC(17,0))'
>
>I do not think that is applicable here
>
>This scenario is to fill a remote view or cursoradapter. In this case the insert goes into the vfp 'cursor'
>
>As to quite often VFP sends them wrongly (say, float for numeric, etc.)
>I have seen this with the sql profiler - but again this is not related to these parameters but to his insert statement

I know for a fact that when we were sending values as parameters for the columns which are defined as NUMERIC(17,0) in SQL Server, VFP was sending these parameters as float (as I observed it using SQL Server profiler). So, I added the 'CAST(?myParam as NUMERIC(17,0))' so SQL Server will always treat these parameters in a correct way. Without that it was implicit conversion which could have been costly.