> If a lookup key should be NOT NULL, then I don't understand why a
> TIB_LookupCombo allows to press <DEL> for retrieving a NULL value.
> Since this not Windows standard to work with a combo box, I don't find
> it user friendly. So I am getting asked by my customers how to remove
> a previously chosen selection from a lookup combo.

I think the original problem here was to cater for people
who wanted to be able to put a NULL value in. I don't think
windows has any 'standard action' to deal with NULL -
doesn't it put in -1?

So the <DEL> was ( I believe ) in answer to a request.

Helen has laid out the best way of using lookups, but it
does not rule ot using the text directly - I need that for
access to an Historic system which falls over regularly if
the wrong text is used, and a lookup is fine, but given the
power of Firebird/Interbase there is no reason to store
duplicate text strings if they are all the same. I have seen
"Account Credit" and "Account Debit" in one Access database
- 100,000 of them in a 32 character field! The programmer
could not see how to use 0 and 1 and output text? ( Then he
was using Microsoft code )

It's all a matter of what we are used to, so pointers to
other ways of doing things can help a lot.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services