Jason,

J> IBO cooperates with the TParams.ParseSQL() method

<SNIP>

If I understand you correctly, this whole process does happen only
when ParamCheck is true, doesn't it?

J> Anyway, without the need to prepare the dataset, TParams will parse the SQL
J> and give you input params. However, these don't have any specific
J> information about the datatype. So, when IBO does prepare the statement and
J> gets back from the server the parameter datatypes I go ahead and modify the
J> TParams objects to properly reflect the data types.

A clever move. Smarter than the BDE here, IIRC.

J> I used to argue that you must prepare the statement before you can work with
J> input parameters and this is true of the native IBO dataset/statement
J> components. However, with the TDataset based datasets it is now possible to
J> work with parameters once your SQL statement is plugged in.

which is a very good thing compatibility-wise.

J> ptInputOutput is when you have an input parameter name that is the same as
J> an output parameter in the result row.

I'm not sure it's at all possible with IB/Fb.

J> I hope some of this information helps to clear up questions about this.

Thanks for the detailed explanation, I'm gonna save it for future
reference.

Ciao
--
Nando mailto:nandod@...