This is a VBS group. You want the javascript
group. I think it's microsoft.public.scripting.jscript
When you get there you should also provide more
information, like what line the error occurs on.
Given that the error starts with 800A I'm guessing
the problem is with Broker.Application, but I have
no idea what that is. If it's some sort of 3rd-party
library you can't expect people to know about it.
But it could just be a 32/64 issue. WScript can be
32 or 64 on Win64, but ActiveX DLLs are in-process
components. They can only run in similar. (32-bit
libraries cannot run in a 64-bit process.) If you
have a 32-bit component you need to use 32-bit
WScript. (You'd probably be well-advised to use
32-bit anyway. Win64 provides both but many
3rd-party components are not available in both.)
I repeatedly forget the wacky folder layout on
Win64. I know that WScript.exe 64 will be in System32,
which is, inexplicably, the 64-bit system folder, while
WScript.exe 32 will be in the 32-bit system folder,
named something like SysWow3264. (?)
--
--
"PeCoNe" <
p.a.m...@gmail.com> wrote in message
news:50f30679$0$31896$c3e8da3$33a0...@news.astraweb.com...