Thanks anyone,
Chris

The "built-in" WScript object is like the ASP objects (Request/Response/etc) or the browser's DOM  objects (window/document).  Each is provided by the host for the script.  Any sample script you see that refers to WScript is an example intended to be executed with wscript.exe or cscript.exe as the host...

--
Michael Harris

  Some of the samples that you can download from the MS/script site run fine
  just using the  WSH, but shouldn't these be "cut and pastable" to add onto
  an asp page?  I've done so and it seems to {*filter*}on the WScript object - I
  assumed no reference, so referenced the WSH Obj model 1.0 and the
  Wscript.exe in the sys32 directory - This appears as WSH 2.0 in the ref.
  selection window.  Yet - still chokes on that object.  Any suggestions for
  me?  I'll continue to debug if my thinking is right that scripts such as
  these are ASPable :)

  Thanks anyone,
  Chris

The other common diff is that ASP uses Server.CreateObject whereas WSH has Wscript.CreateObject
Regards,
Ian
WSH FAQ http://www.*-*-*.com/

  The "built-in" WScript object is like the ASP objects (Request/Response/etc) or the browser's DOM  objects (window/document).  Each is provided by the host for the script.  Any sample script you see that refers to WScript is an example intended to be executed with wscript.exe or cscript.exe as the host...

  --
  Michael Harris

    Some of the samples that you can download from the MS/script site run fine
    just using the  WSH, but shouldn't these be "cut and pastable" to add onto
    an asp page?  I've done so and it seems to {*filter*}on the WScript object - I
    assumed no reference, so referenced the WSH Obj model 1.0 and the
    Wscript.exe in the sys32 directory - This appears as WSH 2.0 in the ref.
    selection window.  Yet - still chokes on that object.  Any suggestions for
    me?  I'll continue to debug if my thinking is right that scripts such as
    these are ASPable :)

    Thanks anyone,
    Chris