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.
On 08/03/2014 11:32 AM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
I want to DECOUPLE that moving forward so that if it a change is
needed in the future, I only need to send the updated error reporting
object. I've created an independent class now (rather than just a
method inside some overall generic system utility object). For
deployment: should I plan to just send the .FXP file for the class,
or create a DLL and send that?
_______________________________________________
Post Messages to: ProFox@leafe.com
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/53df91d0.50...@cullytechnologies.com
** 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.
