>>Like? Were you assuming that the native objects bound to the script executable, like the WshArguments collection, were going to be available without having a running script? AFAIK, 100% of the functionality of the Wscript.Shell, Wscript.Network and Scripting.FileSystemObject, the external objects included in WSH 1.0, worked fine.
>>
>>I've been using the WSH 2.0 beta release for a long time now, and I'm using it pretty extensively.
>
>I don't have the samples in front of me, but I tried to convert some VB syntax to VFP and even had the might John Petersen< g > look at the code. It would not work. I'll see if I can dig it out.

That'd be good, since I've not run into serious problems with it, and ADSI 2.5 is working well, too. You can check the current automation model by grabbing the beta developer version of WSH 2.0 from msdn.microsoft.com/scripting and installing it.