Subject | Re: [IBO] Lookup controls |
---|---|
Author | Helen Borrie |
Post date | 2002-09-10T01:31:58Z |
At 10:55 AM 10-09-02 +0930, you wrote:
value and write it directly onto the parent record - not enforce a
relationship. No double-binding or Keysource-lookup polling as you have
with IB_LookupCombo but better than plain Combobox because it enforces
valid data.
Use KeySource/Lookup and ib_lookupcombo where you need to enforce a
relationship.
Helen
>Helen Borrie wrote:Have another look at Jonathan's requirement: he only wants to pick up a
> >
> > 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?
value and write it directly onto the parent record - not enforce a
relationship. No double-binding or Keysource-lookup polling as you have
with IB_LookupCombo but better than plain Combobox because it enforces
valid data.
Use KeySource/Lookup and ib_lookupcombo where you need to enforce a
relationship.
Helen