Use commitment control to rollback any uncommitted db changes?
-Eric DeLong
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Sent: Thursday, February 25, 2010 8:34 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Uncaught Errors in Interactive Programs and the Users that
Ignore theErrors
I am growing tired of this. An error pops up, the user hits 'C' to
cancel
the program then tries again. Maybe this time it worked, so they
continue on
with their job. The next day, "Why is my data not here?" So now we have
to
back out the changes to allow them to reprocess the data so it runs
correctly.
I am sure I am not unique in this situation. No amount of drilling in to
them will get them to call us when there is an error. They are just
drones
doing what their job is.
So, I know there are a few methods out there on how to "fix" this
problem
(so we know about the problem so we can fix the edge-case bug). I am
thinking I would like to send an email to both developers with the job
log
when such errors happen. By the time we get the email, it may be too
late,
but at least we have something logged.
How would you handle this?
--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark
midrange.com
