Subject | Re: [IBO] Two databases in same project |
---|---|
Author | stanw1950 |
Post date | 2002-01-01T04:53:31Z |
--- In IBObjects@y..., Helen Borrie <helebor@d...> wrote:
phase commit, you'll need to add a TIBOTransaction and set its
ib_Connection and ib_Connection1 properties to IBODatabase1 and
IBODatabase2 respectively. Then, when doing an operation across
database boundaries, explicitly use this transaction, not the
DefaultTransactions that are embedded in the database components...
another, never both. Do I still need the transaction component? I am
still just trying to convert to IBObjects and don't want to get
bogged down with transactions, yet. My project has almost 300 units
in it and I probably haven't even checked 10% yet.
Thanks
> Stan,TIBODatabase components...aren't you? And, if you want to have two-
>
> Just another thought that occurred: You *are* using two
phase commit, you'll need to add a TIBOTransaction and set its
ib_Connection and ib_Connection1 properties to IBODatabase1 and
IBODatabase2 respectively. Then, when doing an operation across
database boundaries, explicitly use this transaction, not the
DefaultTransactions that are embedded in the database components...
>Yes I am. When I do any operation, it will in one database or
> H.
another, never both. Do I still need the transaction component? I am
still just trying to convert to IBObjects and don't want to get
bogged down with transactions, yet. My project has almost 300 units
in it and I probably haven't even checked 10% yet.
Thanks