> Yes, it's this situation. Need I to create relations for
> each field that needs a IB_LookUpCombo?

By "relations" I assume you actually mean queries. I dont mean to be
picky, but generally the term relations is used in respect to the
database itself, creating tables and views in the database. However,
from what you have said I think you mean queries in the client
application (that will select data from relations in the database).

The answer is Yes, you need a TIB_Query for each TIB_LookupCombo.

> But the most fields needs a IB_LookUpCombo! Are there other
> ways? For example in MS Access a lookup combo can have a SQL
> string for source, can I do with the same IBO component?

In the EnhComponents available from the registered users download site
is a component called TIB_LookupEnh BUT all that it will do is allow
you to share a lookup dataset amongst multiple TIB_LookupEnh controls
that need the same data. It will not help where each field has
different requirements.

Most people in client/server situations use surrogate keys. Some
situations require compound keys. Some situations need careful
tuning. TIB_LookupCombo and TIB_Query as a lookup dataset are setup
to support this. A single select statement in the control could not
do this.


Geoff Worboys
Telesis Computing