Displaying execution errors caught in 'try' during development

[Dar Scott]

On Apr 22, 2005, at 10:29 AM, Trevor DeVore wrote:

> I saw the same problem with trying to throw an error from within a 
> catch statement.  What I've done is in the first catch statement I 
> assign the error text to a variable.  Outside the try statement if the 
> variable isn't empty I then throw it.

It works!  Thanks!

I originally checked to see if the environment is development before 
re-throwing.  For libraries, I'm thinking of checking a custom property 
instead.

Dar
-- 
**********************************************
     DSC (Dar Scott Consulting & Dar's Lab)
     http://www.swcp.com/dsc/
     A Sponsor of RevCon West
**********************************************