Marco Menardi wrote:

>
> As far as I understand (and I've learned today), Geraldo wanted to
> tell you that there is no bi-directional link between the two.
> the facts are:
> IB_Query needs a connection AND a transaction
> IB_tansaction needs a connection
> so for every IB_Query you have to specify a Connection + a Transaction
> To make things easier, IB_Connection is provided with
> DefaultTransaction property, so in IB_Query you can specify only
> IB_Connection and leave IB_Transaction property to <default>. That
> <default> is the transaction you have choose as DefaultTransaction in
> the connection.
> So you can have the connection with a default transaction, and specify
> <default> in the transaction property of the ib_query, or specify a
> particular one at will. If you specify as query transaction the
> transaction that you specified as defaulttransaction for the
> connection, I think that it will not hurt, but it's a strange setup.
> mmmm... did I made more confusion?
> hope not ;)
> regards
> Marco Menardi

Hmm. This concept is a bit of a twister.

I understand it as follows. Please correct me if I'm wrong.

The connection has a default transaction, but this property could be set to a component Trans1 if one wants to have
special processing or setup special properties associated with all datasets that use the default transaction, Trans1.
That is, Trans1 becomes the default transaction.

On the same form one could have another dataset that requires a completely different transaction, Trans2, with different
properties and event-processing to the default transaction, Trans1, and both of these transactions could temporally be
open during overlapping periods.

Although it is possible to connect a transaction to a connection and the same connection to the same transaction, it has
the same effect as setting only the default transaction in the connection component to the transaction component.

--
Raymond Kennington
Programming Solutions
W2W Team B