> and check if the assigned ID is 0 to avoid computing a
> discount. The user could have changed this entry.

As Gabriel pointed out this sort of thing can be resolved by triggers
that block changes to the particular record.

I dont see anything strange or difficult about having to insert some
records into a new database. This is pretty much standard procedure
for every database I create. There are usually several lookup tables
that I supply pre-filled with the standard options. The occassional
special lookup record here or there does not seem like too much to
add.

If the problem is that you want consistency of operation (to simplify
training) then perhaps you could try my TIB_ComboBoxEnh control (from
the enhanced components). It operates very similarly to my
TIB_LookupEnh control making the interface very consistent. Of course
this opinion is quite biased :-)


Geoff Worboys
Telesis Computing