> But it is logical for IBO to revert the value of the field back to
> the value specified in the DefaultValues. Why would IBO set the
> field to NULL when I have explicitly told IBO (via the DefaultValues
> entry) that I want this field to be 0 as the default?

My expectation is that delete should clear, remove, get rid of,
destroy, zap etc etc. In none of these do you see the words:
"set some arbitrary default value".

And possibly more importantly: Altering this behaviour now would
break existing production applications - including mine!


Default values are used when inserting a record (but then I think
that has already been mentioned). Any other behaviour you need to
introduce for yourself. Derive your own variation that does what
you want would be my suggestion.

> This characteristic means that if the user inserts and doesn't
> select a lookup-entry the field will be stored as a 0 no problems,
> but if the user inserts, then selects a lookup-entry, then hits
> DEL, a Access Violation is generated. This doesn't make sense and
> is inconsistent.

An access violation? Where from? Whats the call-stack?

--
Geoff Worboys
Telesis Computing