Trigger pgm - SQL errors

Morning list,
I have a customer that wanted to put some kind of security over the GELMAS 
file. We discussed on this thread about using AS400 security. But the feeling I 
came away with was... Be careful be very very careful. And be afraid.
So the route we decided was to put a *read trigger on the gelmas file. Which 
seems to be working perfectly. Whenever anyone reads the file. Like a G/L 
audit. INquiry into an acct, Query the file, Dfu the file. Program works like I 
want it to. 
Now the Problem. 
If I go to AM+ in the browser and click the icon for General ledger I get SQL 
trigger in failed SQLCODE SQLSTATE. 
I can barely spell SQL. So I really don't understand the error message.. But 
the best that I can tell and that Mapics support can tell is that SQL is 
reading records faster than the AS400 trigger pgm can process, and end. I have 
even tried to setup my CL to really do nothing more than cancel if the user is 
QUSER.
Is there a way to tailor SQL to slow down without affecting the other browser 
apps' or any other tricks not to get the trigger pgm to fire?????
 
I am not at that account today so I don't have the ability to test anything.  
TIA
Pete Olshavsky
Ind Mapics Programmer/Systems Analyst


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!