Thanks Aaron. I just didn't realize that to stop the standard error handling behavior, which I admit is better, all I needed to do was handle the onError event. that was the bit I was missing. of course, that's a bother, but it could be done in the class simulating the Try ... Catch.
Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission chip.ora...@psc.state.fl.us (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: Aaron Smith [mailto:aa...@gwmicro.com] > Sent: Thursday, August 20, 2009 4:54 PM > To: gw-scripting@gwmicro.com > Subject: Re: a "standard" VBScript feature won't work in WE > > The example he gives works great for me both in and out of > Window-Eyes. > You'll always get an error because the example causes an > explicit error > to demonstrate the try/catch point he's trying to make. When you get > this error in Window-Eyes, you get the standard Window-Eyes > script error > dialog, which gives you much more control (i.e. stopping, restarting, > etc.). If you ignore the error (which would be the same as confirming > the ok button outside of Window-Eyes), the script continues, > and goes on > to prove his point. > > Aaron > > On 8/20/2009 4:27 PM, Chip Orange wrote: > > Hi GW, > > I wanted to mention a feature of "standard" vbscript, which > I can get to > > work in WSH, but which I cannot get to work in a WE script. > > the feature is based around error handling, which seems to > be different > > in WE. you can read about the feature at: > > > http://my.opera.com/Lee_Harvey/blog/2007/04/21/try-catch-final > ly-in-vbscript-sure > > where it describes a way of implementing a version of "try > ... catch ... > > finally" using a VBScript class. > > I can't do it in a WE script however; it simply halts on > the line having > > the error. I'm not using GWToolkit error handling in any way. > > the Try Catch would be especially useful for handling an > error anywhere > > in an entire block of code (I know you're thinking it's not > worth it for > > a single command). > > thanks. > > Chip > > > > > > ------------------------------ > > > > Chip Orange > > Database Administrator > > Florida Public Service Commission > > > > chip.ora...@psc.state.fl.us > > (850) 413-6314 > > > > (Any opinions expressed are solely those of the author and do not > > necessarily reflect those of the Florida Public Service Commission.) > > > > -- > To insure that you receive proper support, please include all past > correspondence (where applicable), and any relevant information > pertinent to your situation when submitting a problem report to the GW > Micro Technical Support Team. > > Aaron Smith > GW Micro > Phone: 260/489-3671 > Fax: 260/489-2608 > WWW: http://www.gwmicro.com > FTP: ftp://ftp.gwmicro.com > Technical Support & Web Development >
