Helen,

I went back and perfected the forms with tib_ components as given in the
sample. I have nearly everything working as designed (but see more recent
e-mail on this list).

I then saved the form under a different name and began ripping things out,
and adding tiboDataBase and tiboQuery, while keeping the tib_DataSource,
nav/update bars, etc..

At design time I set all the tibo_queries' active properties to true, no
problem. Both data sources point to an existing .gdb. However, none of the
tib_DataSources sees any queries in its DataSet dropdown. What is missing?

Any ideas appreciated.

jwc
-----Original Message-----
From: Helen Borrie (TeamIBO) [mailto:helebor@...]
Sent: Sunday, August 11, 2002 9:12 AM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Login and Data Display


At 09:17 PM 10-08-02 -0400, you wrote:

>Helen,
>
>
> >I have created two forms:
> >
> >Form A, based on the MasterLinks example, with tib_connection, a
> >tib_transaction and three sets of (tIBOtable hooked to tDataSource and
> >tDataGrid). Except for login problems explained below, this is working

ok.

> >
> >2. With tib_connection.LoginPrompt set to false, the default user name

and

> >password properties are not recognized; ditto with a personal user name

and

> >password which ahve been registered with the InterBase server. I get a
> >runtime error, but after closing the message boxes the app opens

normally.

>
>First, I recommend using TIBODatabase with TIBOQuery, instead of
>TIB_Connection and TIB_Transaction. If you need to add more transaction
>objects, you can use TIBOTransaction. The "native IBO" components

(TIB_*)

>that you have used are not incompatible, exactly, but they have less
>encapsulation of the TDataset-compatible stuff which TIBO* components

were

>designed for.
>
>[Jack Cane] >> Understand the first part (database not
>connection/transaction). Just to be clear, you recommend using tiboQuery
>rather than tiboTable? Please confirm.

Well, yes I do...but that wasn't my message this time around. I'd failed
to notice that you had referred to TIBOTable, not TIBOQuery. However, the
same applies, re keeping everything within the TIBO* stream.

TIBOTable exists in the TDataset-compatible stream of components really
just for compatibility with existing BDE apps that people are
converting. In the process of converting say a Paradox app to Firebird or
InterBase one would get rid of table components PDQ. For an understanding
of why, pick up the TI sheet on Moving to Client/Server, from the TechInfo
page.

regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com


Yahoo! Groups Sponsor
ADVERTISEMENT




___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
without the need for BDE, ODBC or any other layer.

___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
keyword-searchable FAQ, community code contributions and more !

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]