Subject Defaults and triggers
Author Gerard J.M.Houtenbos
I use the TIBOTable in a converted non-SQL-application.
I use a field, not null with a default value.
When I insert a record using TIBOTable.Insert and Post without
giving the field a value, then an exception is generated saying
that the field cannot be null.
If I use a SQL-statement to insert the record, then the default
value is accepted correctly.
I have the same experience with Before-Insert-Triggers.

Is this correct or do I make a mistake?