I've seen this question asked on the list a few times, but I've never seen the
answer.
We have a client/server application that, to make a long story short, is inserting
data into the wrong fields of a table. Until we can get an updated version
distributed, we would like to take care of the problem by writing an insert
trigger that calls a stored procedure to update the table so that the values are
in the correct columns (this is what happens when you let an outside consulting
firm write your client/server application!). I've written the trigger/stored
procedure and tested them independently of each other and they work fine.
However, once I call the stored procedure from the insert trigger, I get the
following error:
SQL statement error number -747.
Table or column matches object referenced in triggering statement.
How do I fix this? Is there a work around?
--------------------------------------------------------
Name: Bill Weaver
E-mail: Bill Weaver <billw@fscorp.com>
Date: 12/10/97
Time: 11:00:54
This message was sent by Z-Mail Pro - from NetManage
NetManage - delivers Standards Based IntraNet Solutions
--------------------------------------------------------