> The whole thing should be multiuser safe - I believe commiting all
> changes in a single transaction should ensure that.

I think that disabling a trigger isn't just for that one transaction, even if you do it through execute statement, it's at db level, so while it might be ok for your current transaction to disable it, another transaction might suffer.
An alternative that might work is add a dummy field, which value you check within your trigger, if 1 execute trigger (default value), if 0, just exit trigger. So if you want calculation after bulk insert or whatever, just set field to 0.

just my � 2ct
Dirk Naudts.
ATS Belgium.

[Non-text portions of this message have been removed]