|
>Date: Thu, 10 Feb 2000 07:52:24 -0600 >From: "L. S. Russell" <leslier@datrek.com> > >You know I didn't mean that. > ... >For an error handler to work in all cases it will have to shoot for the >lowest common denominator and that is monitor the error and notify the >user. >If you want to fix the error then you have to get application specific. > >> How can the user possibly know what's the best place to go? If the >> programmer thinks that G is a good place to go back to, then the >> programmer should go there, using '*DETC' on the ENDSR. When quoting my note, you left out this part of your note that I was responding to: "That should work in all cases, just trap the error display the error and let the user choose G, C, D." I thought you meant that you wanted to let the user choose between G, C and D. I was objecting to letting the user choose G. But maybe by "user" you meant "programmer using your general error handler"? Barbara Morris +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.