Subject Re: [IBO] Visibility of embedded LookupCombo
Author Helen Borrie
At 07:47 AM 20/12/2004 +0100, you wrote:

> >
> > Isn't that just what one would expect from such a relationship?
> > It would be logically impossible to select a valid value and keep
> > this relationship intact. The KeyLinks could never be true.
> >
>So, as long as the combo doesn't have the focus, the sql of the n:m tabe is
>in effect, otherwise the one of the lookupcombo.
>Is it all possible to achive what I decribed earlier?

Not by linking. I think you could have the set in a non-embedded
ib_lookupcombo, where you omit the KeyLinks and KeyDescLinks pairs
entirely, and use a method to write the currently-selected lookup value
directly to the field.

To use it as it is designed, you must have a logical relationship between
the KeyLinks pairs, i.e. it must be logically possible to "make" the
relationship. Using NOT excludes that.

Is it the case that you want to form a 1:1 relationship between the two
sets? As soon as a value in the lookup set is selected and applied to the
foreign key in the main set, you want to make it impossible to apply *that*
value to any other row in the main set?