Hello,

I must raise the DefaultValues and LookupCombo issue again,
because (IMO) the functionality is wrong.

For example, if I have a field KEYVALUE which is linked to a
LookupCombo box, I will show 2 examples in which 1 works and 1
doesn't. (DefaultValue entry: KEYVALUE=0, and KEYVALUE is a required
field in the Table)

Example 1 (works):
1) User starts an insert and enters nothing into the KEYVALUE
LookupCombo. (field is blank.)
2) User hits the Commit button.
3) Insert works because KEYVALUE=0 since I have specified that in
the DefaultValues list.

Example 2 (doesn't work):
1) User starts an insert and clicks on a entry in the LookupCombo
list.
2) User says 'Ooops' and hits the DEL button to remove the entry
in the LookupCombo (field is now blank just like in Example 1).
3) User hits the Commit button.
4) A IBO EIB_DatasetError exception is generated saying 'KEYVALUE
is a required field'. This is because hitting the DEL button sets
the KEYVALUE field to NULL.

There are only 2 possible solutions:
1) IBO returns the KEYVALUE field to 0 after the user hits the DEL
button since this is the DefaultValue that I have specified the
field to have. This is the correct thing to do.
2) I have to put logic in every one of my BeforePost events and
check the value of every one of my LookupCombo fields to see if they
are NULL and change them to 0. This is what I must do now, and is
not the correct solution.

Eric.