There is a LARGE open source component library called "Jedi Visual Component Library". Within this library there is a component called "TJvDBLookUpCombo" that works fine. I guess it uses TDataset so you can do a lookup on Tables or queries.

Beside everything, this library is VERY COMPLETE and I have found many godd components in it.

Regards
Jay

----- Original Message -----
From: mspencewasunavailable
To: IBObjects@yahoogroups.com
Sent: Friday, September 08, 2006 7:34 AM
Subject: Re: [IBO] TDBLookupCombo can't use a TIBOTable...


--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 01:37 AM 7/09/2006, you wrote:
> >because it wants its DataSource to be connected to a TTable
> >descendant. I looked into using TIB_LookupCombo, but *that*
doesn't
> >seem compatible with TIBOTable because it insists on a
TIB_Datasource,
> >which doesn't see any TIBOTable in the designer.
> >
> >I can't be the first to encounter this. Is there a standard
> >workaround?
>
> No. They are two distinct series of components. TIBO* components
> are VCL-control-compatible via TDatasource; TIB_* components are
> "native IBO" and are not VCL-compatible.
>
> At the data access level you can pass the SQL in its current state
> between a TIBODataset and a TIB_Dataset (in either direction)
using
> AssignSQLWithSearch. By this means, for example, you can produce
> reports using VCL tools, where the data originated in a TIB_Query.
>

Sorry, I wasn't clear. I only mentioned the TIB_* components to
indicate that I'd looked into using them and found that they
probably weren't suitable (for the reasons you explained).

My original question remains: What do people usually do when they
have to convert a TDBLookupCombo, which insists on a TTable
descendant for its lookup property, when they want to convert to
TIBOTables. Since there will only be a handful of entries, I'll
probably just change to an appropriate non-DB aware control and
handle things from there, but I was hoping there might be a trivial
workaround.

Michael D. Spence
Mockingbird Data Systems, Inc.






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