Global Error Trapping

Andrew Clague

New Member
Hi, hope you can help :)

Problem

We have a large(ish) application approximately 10,000 programs / windows, we encourage our users to report any Progress errors (such as a 'find first/last failed' error) to the developers so suitable action can be taken, unfortunately we find that our users do not always report such errors. I recognise that the errors could be trapped individually if all code was written perfectly but with so many programs we cannot gaurantee this is the case.

Is there a way in Progress of writing code that can be added as a 'global error trigger', what I'm thinking is something like (bad pseudocode !);

In the main window, i.e the window from which all other programs are called;

on error condition anywhere in system do:

create error_log.

error_log.user = current user.
error_log.error_type = error type.

end.

Such that if any error occurs anywhere in any program an error audit record would be created, using the 'error:status' 'error:num-messages' etc. to get useful details.

Any help or advice would be much appreciated.

Thanks
 
Back
Top