Maybe something along the lines of the old c code trap: #ifdef USEDEBUG #define DEBUG(x) x #else #define DEBUG(x) #endif
might be worth looking into. Claude Stone <[EMAIL PROTECTED]> wrote: I have found that including an exception statement in each routine will direct me to the routine and then troubleshoot by breakpoints. IE: Exception MsgBox "Unhandled exception error in routine xyz" At 08:32 AM 12/2/2006, you wrote: >I'm sure that I'm not the only one who finds error trapping a tedious >process. Does anyone know of any classes or plugins that will help take >care of this automatically? > >Any input would be appreciated! > > >RB5.5.5 and a mostly unused copy of 2006r2. >WinXP, 2.2 GHz, 2G RAM > >_______________________________________________ >Unsubscribe or switch delivery mode: > > >Search the archives of this list here: > > > >-- >No virus found in this incoming message. >Checked by AVG Free Edition. >Version: 7.5.430 / Virus Database: 268.15.3/562 - Release Date: >12/1/2006 1:12 PM Claude Stone _______________________________________________ Unsubscribe or switch delivery mode: Search the archives of this list here: --------------------------------- Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
