> Thing about that table that requires, forced by integers, that records
> are entered by the user in a certain order. It works ok. But if you
> have to automatically "pump up" (already correct and fine) data in
> that table with "insert from...", you can't do it in the correct
> order, so trigger protection fires.

I don't think that is something that would come up in for
many of us. Since there is NO natural order in a relational
database, the order is always controlled by an index. While
I can see that you have designed yourself into a corner, I
suspect that the correct way around it is to use a pump such
as in IB_SQL and create the source query with the right
order. This would then allow you to observe and handle any
problems that arose during the pump, something that can not
be catered for in a blind dump.

If your triggers are so 'protective', I could see the
database 'locking up' and I would not expect the engine to
be able to sort things out on it's own, so maybe you need to
review how the data is loaded?

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services