It is totally up to how you want to design your application whether or not
your transaction connects to more than one database or not. This is a
design decision. If you are using more than one connection they both have
to be connected for the transaction to be started.

Jason

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Steve Harp
> Sent: Thursday, May 05, 2005 7:47 AM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] DatabaseName cannot be blank?
>
>
> --- In IBObjects@yahoogroups.com, "Jason Wharton"
> <jwharton@i...> wrote:
> > > I may have fixed it. All I did was move the 2nd TIB_Connection
> > > component to a different data module. Apparently, when 2
> > > TIB_Connection components are in the same data module, things get
> > > confused. Sounds like a bug to me.
> >
> > If you feel it is a bug I'd like to see a little sample app that
> > demonstrates it. My hunch is you have a transaction that is wired
> to both
> > connection components somehow and it is actually trying to open the
> second
> > connection. Any chance you could at least get the callstack on that
> > exception so we can see what chain of events leads up to
> the attempted
> > connection of the second connection component?
>
> The TIB_Transaction is being shared by both TIB_Connection components.
> Should I use different TIB_Transaction components for each
> TIB_Connection component? If so, why does the TIB_Transaction
> component have IB_Connection, IB_Connection1, and IB_Connection2
> properties?
>
> How do I go about getting the callstack for you?
>
> Steve