Subject | Re: [IBO] DatabaseName cannot be blank? |
---|---|
Author | Steve Harp |
Post date | 2005-05-05T14:01:23Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
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.
Steve
> At 12:08 PM 5/05/2005 +0000, you wrote:when it
> >--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> > > At 01:00 AM 5/05/2005 +0000, you wrote:
> > > >Hi All,
> > > >
> > > >I've started getting this error with an existing application
> > > >tries to open a TIBOQuery object. I don't understand the errorTIBOQuery
> > > >because the DatabaseName property for the TIB_Connection and the
> > > >TIBOQuery are both set. In fact, the DatabaseName for the
> > > >is populated automatically when the IB_Connection property is set.things up?
> > > >
> > > >I'm sure this is a simple fix, but what have I done to screw
> > >IDE and
> > > Check whether you have inadvertently deleted/altered any of the
> > > TIB_Connection properties Path, Server or Protocol.
> > >
> >I'm setting Server, UserName, Password, Path, PageSize, and Protocol.
> > Besides, the TIB_Connection object is openning without errors; it's
> >the TIBOQuery object that's failing. The TIBOQuery object has the
> >IB_Connection property set to the TIB_Connection object which, inturn,
> >sets the DatabaseName property.
>
> This sounds fuzzy. TIB_Connection constructs DatabaseName in the
> ignores it thereafter. You can use it for a "friendly name" of yourIB_Connection. IBO
> choice, if you wish.
>
> If you're using an IB_Connection object instead of a TIBODatabase, then
> drop a TIBOTransaction into your datamodule. Set its IB_Connection
> property and, if you are only using a single transaction, select this
> transaction for your IB_Connection's DefaultTransaction.
>
> Set the IB_Connection property of the TIBOQuery to your
> should then do all the necessary things and make sure that the query isI may have fixed it. All I did was move the 2nd TIB_Connection
> linked to the right database.
>
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.
Steve