Re: SQL Proc and Call Statment

Why does file B cause an issue?

Do you fear that the fact that the trigger program may have a record lock 
and then update program may try to do something and conflict?  Remember, 
the trigger runs sequentially.  Therefore it won't return to the calling 
program until it is completely done.

Do you fear that the calling program may already have a record lock thus 
conflicting with the trigger program?  If so, then having the trigger put 
off the access to B to a data queue or anything may not buy you anything 
if don't free up the lock in the original program before the data queue 
processor tries to access B.

Rob Berendt