At 05:14 PM 1/06/2006, you wrote:

>Hans (and all),
>
>I implemented this solution but I'm contemplating about the following:
>
>1) What situations cause the Default setting in FB to be ignored, as
>I've experienced? Is IBO the one in play here?

No, it's DB rules. The default applies only to inserts, and only
when the defaulted column is not present in the INSERT
statement. You can involve the client in the defaulting process if
you want to, by applying a default at the set level (in
ColumnAttributes) or by intercepting at BeforePost and applying the
server defaults. The problem with GetServerDefaults is that it's
noisy on the network. The advantage, though, is that your
application isn't the one that's applying business rules that rightly
belong in the database.

>2) I have some more numeric(15,2) fields in the db. Adding two
>separate triggers for each affected tables add to the overhead when
>inserting/modifying records. Or am I overstating?

You're overstating grossly. The server is just being asked to do its
stuff - it's a drop in the bucket compared to relying on the client
to do it (local and network overhead) AND the integrity is protected.

Helen