Helen Borrie wrote:

>
> At 10:55 AM 10-09-02 +0930, you wrote:
>
> >Helen Borrie wrote:
> > >
> > > At 08:17 PM 09-09-02 -0400, you wrote:
> > > >Hello:
> > > >
> > > Sure. If you are just going to use the lookups this way (i.e. static
> > > values) then use an IB_Combobox. In your FormCreate, just pull the values
> > > in via a TIB_Cursor and feed them into the Items of the combobox.
> >
> >I'm used to this being done automatically with IP's wwDBLookupCombo.
> >
> >Wouldn't the IB_LookupCombo be better to use in this case?
> >
> >Wouldn't it be populated automatically?
> >
> >Couldn't one link the text field of the parent table with the single field
> >in the lookup
> >table?
> >
> >Or is IB_LookupCombo only suitable for linking an ID field with an ID
> >field and displaying
> >the text of a different field in the lookup table?
> >
> >Why did you not consider the use of the IB_LookupCombo?
>
> Have another look at Jonathan's requirement: he only wants to pick up a

(unnecessary)

With wwDBLookupCombo I'm able to specify the looked-up field as the same as the displayed
field and it this same field that is stored in the main table.

This is the simplest case of such a lookup and ought to be possible as it would fill the
lookupcombo automatically.

Also, with wwDBLookupCombo one doesn't have to open the table as it does so automatically.

I guess I'm suggesting an enhancement be made or a new component that automatically loads
the lookup data from the specified table when needed.

Raymond Kennington