>>I was hoping you'd see this. I didn't think that you'd find this behavior with the FSO. The connection, obviously, is the "WScript".
>
>Right, but why only the network and shell objects and not wscript.file, etc? Oh, well, I bugged it, and we'll let Calvin figure it out. :-)

I'd make the SWAG that it has something to do with the fact that wscript, within the WSH, is in and of itself an object with its own PEMs, and this may have something to do with that.

As for Calvin, does this mean he gets more vacation time?< bg >