Dawn,
You have to be careful about using triggers to alter the table on which the trigger is based. We do this, but only to update the row that triggered the action in the first place by using "where current of ..." This will not cause the trigger to fire again. (In our case we're updating the row that fired the trigger to indicate that it has been "posted.")
If you use a trigger to do further inserts or updates to the table that fired the trigger, that action will itself fire the trigger which can then fire the trigger, etc. Much like the mirrors in a hair salon where the reflections eventually stop because of the accumulated opacity of the glass.
Your solution of using a temp table is probably the best approach.
results. I suspected the triggers were the issue so I removed the triggers from the table, and voila no errors. So...is it not a good idea to trigger a cursor on a view that contains the table that has the trigger? (I feel like I've read that in a Dr. Seuss book!) Or is that OK, and I have a different problem?
Dawn
Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]
