Hi Craig,

Still cant get through on private email so here is my response - my
apologies others not interested in the TIB_LookupEnh component.

> I need to know when a search in your
> TIB_LookupEnh fails. In TIB_LookupCombo,
> Jason has included an event called
> OnNotInList that I use quite a bit ...
>
> For example, I have a CityStateZip lookup table that
> simplifies data entry. When editing the master
> record and typing in a Zipcode, the City and State
> fields are imported from the Lookup table if that
> Zip exists.
>
> If the Zipcode is 'NotInList', then a New Zipcode
> form is displayed for the user to complete.
>
> So, how can I know when a lookup fails using
> TIB_LookupEnh?

This is one thing that I have not quite worked out. At the moment the
lookup never fails, it defaults to just grabbing the nearest entry. I
spent a long time discussing this with my clients and they decided
they did not want the user automatically creating records just because
they happened to mis-key the input. There was too much room for
error, by forcing the users to an independant create process we were
able to force them to be more careful with their inputs.

However that does not help you, since not all clients will agree. I
think that what Marcin is doing is using the second button capability
to provide an explicit button for the user to decide when they want to
create a new record - this is my preference.

I can put a NotInList event on my list of things to do, but I am not
sure how long it will take to implement. The control processing is
quite convoluted and it is easy to break things when fixing something
else.

I am hoping to release an update tonight - including some of your
earlier suggestions and also some of Marcin's suggestions.


Geoff Worboys
Telesis Computing