> I would prefer a property in TIB_LookupCombo 'EmptyString' where one
> can enter a string (i.e. "<none>") which is displayed in the combo so
> the user can select it. And the result is a NULL value in the
> associated column.
> No need to insert a NULL entry in the lookup table.

All my lookups have the 'Blank Line' as a table entry, but I
than associate other information which may be needed, such
as in your exanmple I would have 'No Topping' in a second
field of the lookup table, to use as a Hint, etc. Then I
don't have problems if I create a concatonated string which
may contain the 'Blank Line'.

Do you really need ( or want ) NULL in the table for that
entry? I do find it more of a hindrance than a help.

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