Permit me to rephrase part of this:
"... apparently the SQLCODE when tested by the code that performed the
original insert MAY COME BACK other than 0 ..."
Here's another one where I would appreciate some thoughts.
Table A has an INSERT trigger. The trigger writes an audit record to an
SATTACHed table.
The problem is that one cannot now rely upon testing SQLCODE = 0 in this
context; apparently the SQLCODE when tested by the code that performed the
original insert comes back other than 0 even though the trigger performed
exactly as expected.
Is there a way in this context to retain the original SQLCODE or suppress
the effect of the trigger on SQLCODE? I have to admit that none of that
sounds possible to me, but maybe someone has some thoughts.
Also, can one expect the effect on the ERROR VARIABLE to be the same as on
SQLCODE in this context?
Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
