I have been able to duplicate the error. I created a test DB, with two tables. In Table 2 I put a insert trigger that just modifies a value in Table2. In Table1, I put and insert trigger to insert a value into Table2. Both triggers pull from the inserted table.
There was no problem as long as the ID fields in the two tables were the same (they were both blank to start with, and so the IDs started out the same.) As soon as I put an entry into Table2 that was apart from Table1 thier ID filds were no longer in sync, and the next entry into Table1 produced the same error I am getting in my other DB.
How can I handle nested use of the inserted table? I believe that is the problem here.
Thank You
Rollin Burr
Politicians and diapers have one thing in common. They should both be changed regularly, and for the same reason.