Moreover...I'm thinking that you of course pass the parms like any usual
ON ERROR DO ErrHand WITH ERROR(), MESSAGE(), PROGRAM(), LINENO(), but if
you don't pass the parms, the APP launches a management kind of form
that allows you to review the log of errors.
Kevin -- to address what Ferd said, do you return control to your app or
is it Game Over when they hit an error?
Thanks,
--Mike
On 2014-08-04 11:36, [email protected] wrote:
On 2014-08-04 09:59, Kevin Cully wrote:
In the past, we've decoupled our error handler into a Foxpro based APP
file. It worked out well.
[1] Create a project such as 'ErrHand.pjx' with all of the forms,
programs and reports that are needed for a bulletproof error handling.
[2] Build using BUILD APP ErrHand FROM ErrHand
[2] Test the dickens out of it.
[3] In your main application, change error line to ON ERROR DO
ErrHand.APP WITH {parameters usually found in VFP}
Worked nicely. I could update the ErrHand.app without affecting the
main application, or more likely, update the main application without
needing to touch the ErrHand.app.
HTH.
That's exactly what I'm looking to do. Thanks, Kevin!
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
