>>I'd appreaciate it. This area is really beyond my knowledge of the WSH. I really don't know, under the circumstances, if remote automation will work. If Rick says that browser security is going to be an issue, then that's the end of it. No ifs, ands, or buts about it.
>
>Well, the blurb on remote automation is just that, a blurb. Apparently the real issue is instantiating the object on the remote computer. After that, it must be just like manipulating it locally.
>
>I tried to use VFP on my local machine and CREATEOBJECTEX() to instantiate a WSH object on the little web server in my cube, but couldn't get it to work. At first I thought I wasn't using the proper "computer name", but I don't think that's so cause I tried it using the IP address of the computer which is supposed to be legal, but that didn't work either. Keeps giving me a "Class not registered" error. So either there's something wrong with my statement or there is a security issue. I haven't done any DCOM related stuff, so this is pretty new to me. My gut feeling is it's security related but I just don't know right now.
The Script components live in wshom.ocx, which is an in-proc server (dll). In-process servers cannot be configured to run remotely unless packaged in MTS.
Even if WSH was an exe, each client machine would have to be configured to give you rights to run it remotely. (DCOMCONFG). Not too practical.
Erik Moore
Clientelligence