> What are the advantages of your TIB_LookupEnh-Control ?

The primary advantage (and the reason I originally built it) is that
it does not activate the lookup table unless it has to, and it will
deactivate the lookup table when it is no longer required. This can
make quite a big difference on a form with many lookups. It is also
handy because you dont need to remember to manually activate your
lookup tables before using them.

Since then I have extended the lookup so that two or more lookups can
share the one lookup dataset (each control has its own
KeyLinks/KeyDescLinks properties for use in this mode).

There are some situations where the above features cannot be used.
For example, if you have two lookup datasets interacting in
master/detail mode, then the master lookup dataset should not be
deactivated by a lookup control or the detail lookup dataset will not
work. In such situations you simply set the LookupDeactivate property
to false.

The control also supports searching against a compound (usually
computed) field. Its a bit hard to explain, so I'm probably the only
one using this feature :-)

The control reacts a little differently to TIB_LookupCombo as well.
Whether this is good or bad is a matter of taste :-)

HTH

Geoff Worboys
Telesis Computing