> or by setting the NOTREQUIRED column attribute for the
> specific columns.

This seems to be an interresting option.
Thank's for the hint.

Another good suggestion I tried came from Helen.
This was to enter your own InsertSQL statement and remove
the columns.

> Your other alternative is to provide defaults at the client itself,
> using the DefaultValues property.

I don't like this kind of solution because in my opinion it breaks
the c/s design.

Thank's again both for your suggestions.
Regards,
Frank Gruber