Re: Catching errors on user screens

In a similar situation with the mandate of "we don't modify vendor code" I
used a trigger on the file with the disasters.  At least that way I could
stop their program and alert them.    In that instance I used a *BEFORE
trigger and if they were using invalid data I could have them do it over and
over til they got it right.  The audit journals were inaccurate for that
entry of course but the client preferred that to busted production.  In your
instance I suppose you could have a message sent to your screen saying "Go
see User X.  S/He's doing it agaIn"
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: Thursday, June 26, 2003 3:52:29 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Catching errors on user screens
 
Hiya,
 
well, as one of our apps we have an old BPCS implementation. The users of 
the app are very inexperienced and tend to create lots
of user problems. 
Worst of all, when one of the programs crashes, they just ignore the 
problem and press enter until the error screen goes away. When
I'm lucky they will call they had a problem, but normally they wait until 
consequential errors occur.
 
Any trick to stop these users cold at the error screen? I preach to them 
every other day to at least press 'D' and Enter, so I get a dump.
But most of the time they'll just do enter.
 
Thanks,
 
Oliver