>>>>>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))'
>>>>
>>>>Try this with german standard
>>>>
SET POINT TO ,
>>>
>>>I don't understand this reply. Did you mean another thread?
>>
>>Iif you cast to numeric and create a string out of it it will respect SET POINT. Then you have two fields out of one.
>
>I'm not proposing to pass it as a string. Re-read my suggestion one more time.
Now I'm puzzled. You wrote to have 'cast(?mProperty as NUMERIC(17,0))' inside mProperty parameter?
Like
mProperty = 'cast(?mProperty as NUMERIC(17,0))'
?
or do you mean as part of the sql string, replacing
?mproperty with
'cast(?mProperty as NUMERIC(17,0))'?
But this would just enter the string.
Like in
INSERT INTO xyz (field) VALUES ('cast(?mProperty as NUMERIC(17,0))')
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]