Hello Jason

It seems that you modified the way IBO works with columns' default
values. And it also seems that you made a step too far ;-).
If a column is based of domain with default value this default value is
taken when adding new record (previously IBO was keeping null value),
but what is more annoying that IBO sets the default value for
parameters.
I have a stored procedure that has and integer parameter based on domain
with 0 as default value. Procedure is prepared to accept null value in
this parameter and 'behave' accordingly. What was my surprise when IBO
set 0 for this parameter 'without asking'

So, could you reconsider your changes? :-)

Thanks
Marcin