Lester,
thanks for replying.

>> I have a TIBOQuery whose SQL property is something along the lines of
>>
>> 'execute procedure someproc(?, ?, ?, ?)'
>>
>> and whose Params property correctly holds 4 hand-crafted TParam
>> objects (one for each ? in the SQL string).
>> ParamCheck is False since I am not using param names in the
>> SQL string hence I avoid the parsing overhead. Plase bear with me this
>> actually makes sense in my application.

LC> So you are not passing Params?

I am:

>> I have a TIBOQuery whose SQL property is something along the lines of
>>
>> 'execute procedure someproc(?, ?, ?, ?)'
>>
>> and whose Params property correctly holds 4 hand-crafted TParam
>> objects (one for each ? in the SQL string).

LC> My understanding of ParamCheck was that it would freeze
LC> updating Params until all params had been updated.

I don't think I understand what that means, anyway ParamCheck's job is
to make the dataset refrain from searching (and parsing) the SQL
string for param names in order to create TParam objects.
It should not stop the component from considering the TParam objects
that are put in place by hand.

This is what the BDE help (which is said to represent the reference
for IBODataset) has to say about it:

Set ParamCheck to specify whether or not the Params property is cleared
and regenerated if an application modifies the query’
s SQL property at runtime. By default ParamCheck is true, meaning that
the Params property is automatically regenerated at runtime.
When ParamCheck is true, the proper number of parameters is guaranteed
to be generated for the current SQL statement.

LC> So why do you think you want ParamCheck false?

I said bear with me it makes sense. It's just too long to explain and
I don't think it's important. It should just work as advertised, so to
speak (while I agree it's not common practice). :-)

Ciao
--
Nando mailto:nandod@...