Can't use Wscript.Shell when moved to Win7 x64

[makotech222]

I'm very new with VBscript, and the guy who wrote this has left. I'm not sure exactly whats happening when Wscript.shell is being created. Can i specify the location of Wscript.exe?

I've already tried specifiying the location of cmd.exe to both the x64 and x32 versions, to no avail.


One other thought, i was thinking its possibly related to administrative privileges. Even thought on my machine, UAC is set to none, and i'm on the admin account. Could that still be causing problems on Visual Build?

[kinook]

WScript.Shell is an object available in script code (provided by Microsoft).
http://msdn.microsoft.com/en-us/libr...=vs.84%29.aspx

There's also a wscript.exe and cscript.exe (again, from Microsoft) for invoking scripts from a command-line.
https://support.microsoft.com/kb/232211

WScript.Shell is not even needed in Visual Build to run a program. You can use a Run Program action or a Builder.RunProgramEx call (from script code).
http://www.kinook.com/VisBuildPro/Ma...gramaction.htm
http://www.kinook.com/VisBuildPro/Ma...amexmethod.htm

As to the actual problem, I still don't know what it is so can only guess. A privilege issue is one possibility. At any rate, it sounds like a Windows issue, not a Visual Build problem per se.