At 02:07 AM 1/10/2003 +0000, you wrote:

> > fwiw, TIB_DSQL is a much more elegant component
> > for performing Execute statements.
> > Hook its ib_Connection property to your TIBODatabase; and
> > read output from its Fields[] object (not Params[]) after
> > execution.
>
>Thanks for the advice. Being a new IBO user I assume that the TIB_
>flavour should be used in preference over the TIBO flavour where a
>TDataset decendant isn't a requirement. Is this true?

True, mainly, i.e. if the output doesn't have to be managed by a Datasource
component, you don't need the extra overhead of the BDE-style component.

Another consideration is that Native IBO doesn't use TField objects
(instead, it works with arrays of TIB_Column objects and descendants with
some brilliantly specialised behaviours...). If you need to keep some form
of code dependency on an instantiated TField descendant, then you have a
reason to use the TIBO version. But experience shows that, once you begin
harnessing the power of TIB_Column and its children, you'll choke on being
tied to the TField objects.

heLen