Geoff,

>I see the setting of null string fields to blank as a specific
>requirement in itself - quite separate from wanting a "default" value.
>By doing this in the triggers I can be sure that there are no null
>string fields in my table and therefore any stored procedures that I
>write can assume a non-null value. This allows code like...
>
>If you are content with your solution that is great. Just be careful
>if you or anyone else ever edits/inserts fields from IB_SQL or some
>other utility.

That is why I have the columns defined as NOT NULL. I was under the
impression initially that the database would use the defaults instead of
the null values on the insert. Hence my initial problem.

Thanks for the input,

Allen.