I have some stange effects using VBScript on Vista: I'm sure it's just
settings but I nned some guidance.



1) If I run VBscript as a vbs, no errors are reported, scripts just die and
depart without a funeral.

2) If a script is run via the script control, errors are reported normally.

3) I have a third party tool that executes scripts to customise forms, it
too reports errors

4) If I turn on JitDebug in the registry, All error reporting of any kind
stops, but the script debug tool, that every preceding version of windows
has, isn't invoked.

a) How do I persuade VBS to have a funeral for scripts: nice message like in
other Windows please?
b) how to I persuade JitDebug to invoke the script debugger?

Thanks

Obvious question - but I'll ask anyway. Did you comment out all the
"Resume on Error" statements in your script and try running it again?

I don't use Resume on error unless I really have to, usually when accessing
things that aren't always there. The same script executed via vbs double
click fails to fail, but under the script control fails beautifully, or on
XP fails as expected. It's only on vista that failure isn't reported, or if
i put jitdebug on. I'd run everything under the script control if I could
figure out how to instantiate wscript under vb6 ( or .net)
A
<gimme_this_gimme_that@xxxxxx> wrote in message
news:8a19e631-f5ac-4d44-a0b1-7a0d82343d86@xxxxxx

> Obvious question - but I'll ask anyway. Did you comment out all the
> "Resume on Error" statements in your script and try running it again?

On Mar 21, 9:39 am, "Alan Gillott" <argillot...@xxxxxx> wrote:

> I don't use Resume on error unless I really have to, usually when accessing
> things that aren't always there. The same script executed via vbs double
> click fails to fail, but under the script control fails beautifully, or on
> XP fails as expected. It's only on vista that failure isn't reported, or if
> i put jitdebug on. I'd run everything under the script control if I could
> figure out how to instantiate wscript under vb6 ( or .net)

I don't use vista (I'm on XP), but if you want to instantiate
WScript...
Check out my 1st post (on March 6, entitled Inducting WScript;
from the thread started on Jan 29 titled: Microsoft Script Control)
which describes how to do this for non vbscript processes.

Csaba Gabor from Vienna

> A<gimme_this_gimme_t...@xxxxxx> wrote in message
>
> news:8a19e631-f5ac-4d44-a0b1-7a0d82343d86@xxxxxx
>

> > Obvious question - but I'll ask anyway. Did you comment out all the
> > "Resume on Error" statements in your script and try running it again?

Try running the script from command.com using both csript.exe and
wscript.exe - see if one works and another doesn't.

All very well, but it doesn't explain why jitdebug isn't firing up the
script debugger? Just ingibiting errors.

<gimme_this_gimme_that@xxxxxx> wrote in message
news:609d0482-79b9-45bd-bb59-50fa59d28dfe@xxxxxx

> Try running the script from command.com using both csript.exe and
> wscript.exe - see if one works and another doesn't.

Alan Gillott <argillott.x@xxxxxx> typed:

> All very well, but it doesn't explain why jitdebug isn't firing up the
> script debugger? Just ingibiting errors.

Indeed, it is just a little to late for a reply, but I want to attempt
it once again. The MS Script Debugger was from the outset a dumb piece
of software which has never properly worked. The programmer(s) would
have had to present him-/themself more time to debug all errors.
However, presumably he/they did not have them, and since then everything
has remained as it was right from the start, being in its infancy.

AFAIR for debugging scripts with this odd software you have to call the
scripts with both debugging switches simultaneously:
CScript.exe //X //D myscript.vbs

But I am not really sure, it is already quite a while that I can be
irritated by this program and annoyed, when it's crashed every time!
Ehm, sorry for my poor pronunciation, otherwise it's not my mother's
language.

--
ЯR