At 01:54 PM 5/11/2003 +0000, you wrote:

>I have previously only been using the IBOxxx components (since I use
>DevExpress), however since I have learned the IB_xxx components
>offer some speed improvements over the IBOxxx components I have
>begun mixing these within the same application (only using the
>IBOxxx for those things that NEED to be connected to the GUI).
>
>As of now I am simply using the TIBODataBase I have been using all
>the time (before trying out the IB_xxx components) and this works
>OK. I just want to know if I would have some benefits using
>TIB_Connection or TIB_Database in stead !?

It depends. TIBODatabase is fine for hybrid applications such as you are
doing. It is a TIB_Connection descendant and the non-buffered TIB_
components are quite at home with it.

TIBODatabase mimics the VCL model of one transaction/one
connection. However, the TIB_Connection handles multiple transactions, and
the TIB_Transaction handles multiple connections. Unlike TDatabase,
TIBODatabase *can* take additional transactions (that's what the
TIBOTransaction component is for), though (IMO) it is messy.

If/when you get into multiple connections and multiple transactions, it
will simplify your application architecture to use separate TIB_Connection
and TIB_Transaction components instead of the composite
connection/transaction component. Your TIBO* datasets can connect to
TIB_Connection via the IB_Connection property and you can manage their
transaction side explicitly, via the IB_Transaction property.

I'm figuring that you are clicking onto the power of the non-BDE model so
fast that it won't be long before you start looking into the benefits of
multiple transactions.

Helen