RE: Ending a VB Script Macro

["Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>]

Yep - I suppose that's what I'll have to do - your right
it's very "ugly" method.

I did a search on the MS TechNet site for "ending a vbscript" 
and it lead me to this page

http://www.microsoft.com/technet/scriptcenter/resources/qanda/aug04/hey0
830.mspx

which seems to indicate that the statement:

Wscript.Quit 

will terminate any WSH script immediately. I'm not sure what 
the difference is between a Visual Basic script and a Windows
Scripting Host script. I thought they were executed by the
same process.  Needless to say, this method did not work.

It's a shame that there aren't better references/tutorials
for running VB scripts under Client Access. It seems to be 
a very powerful method for interacting with a display session 
and automating a lot of mundane work.  

Anyway, thanks for your input (again)!

Terry

> -----Original Message-----
> From: pctech-bounces@xxxxxxxxxxxx 
> [mailto:pctech-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
> Sent: Wednesday, November 16, 2005 8:39 AM
> To: PC Technical Discussion for iSeries Users
> Subject: RE: [PCTECH] Ending a VB Script Macro
> 
> 
> I hear you, Terry. Can you set up control blocks (IFs, SWITCHes - 
> like SELECTs in RPGIV) so you could merely drop through and just have 
> the routines end? More work and not so pretty sometimes, of course.
> 
> At 07:23 AM 11/16/2005, you wrote:
> 
> >Vern, thanks for the reply.
> >
> >I have tried the "Exit Sub" statement but I wanted to
> >avoid having to set a global variable to monitor for
> >termination in each nested subroutine :(
> >
> >I suppose I'll have to re-think the design of the script
> >since it was written by a "top down" programmer ;-)
> >
> >Terry
> >