> Hi Ken,
>
> After you gave this answer to Tiemo about a week or so ago, I decided to
> play with running some vbscript out of rev 2.9+. The only thing I get is
> "execution error." I tried your above script and get the error and then
> reduced it down to two hard coded lines:
>
> put format("s
Hi Phil,
> Have you tried "putting" tVBS just before the "do" to see what the VB
> script looks like?
No, but I had put in a breakpoint. ;-) The script looked fine. And, as I
said, suspecting line endings, I tried CRLF, etc.
> You might see some obvious thing malformed. Or is it
> possible ther
Hi Jim,
Have you tried "putting" tVBS just before the "do" to see what the VB
script looks like? You might see some obvious thing malformed. Or is it
possible there's a permissions issue? Stranger things have happened. I
just automatically suspect permissions if the script is correct. Is your
Ken Ray wrote:
> Here's how it would be done in Rev 2.9+:
>
> on VBS_AppActivate pTitle
> put format("set WshShell = WScript.CreateObject(\"WScript.Shell\")")
> into
> tVBS
> put tVBS & cr & "WshShell.AppActivate" && quote & pTitle & quote into
> tVBS
> put tVBS & cr & "result = Err.number
Hey, Tiemo...
> My questions are not going to my code, but to some principles with calling
> the shell wscript.exe
Are you using Rev 2.9 or later? If so, you don't need to call the shell()
command for VBScript; you can "do
Hi Tiemo,
> I have an updater in my app, which makes under Vista the file update
> with
> VBScript because of the UAC. My updater works in most cases fine. But I
> have
> a certain number of Vista customers, where It doesn't work at all and I
> am
> not yet behind, what is going on there. The upda
