I had the script below running from an internal web page
that calls the script. There is other code to change
registry settings that has been stripped out. This
portion of the code was running fine with Office 2000.
We moved to Office 2003 and the script won't open the
spreadsheet now. Is there something new about the shell
command or wscript file in 2003 that would not allow this
to run???

dim direty1
direty1 = "T:\IncidentReporting\Reports\safety.xls"
Set shell = CreateObject("WScript.Shell")
shell.run direty1

Thanks in advance for any help!!
Gordon Cashmore

I found the same problem runnning your script from a VBS. After some
hacking I went into the registry he

HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\command

and renamed the Command key to Commandx so that the "default" command was
used. After that the file opened from the script. Not much of a solution I
know.

An alternative from a VBS is using automation:

Dim XL
Set XL = CreateObject("Excel.Application")
XL.Workbooks.Open "c:\Book1.xls", 3
XL.Visible = True

Whether this is a viable alternative for your purposes I don't know.

--
Jim Rech
Excel MVP

Thanks for the help. The create object worked for me
instead of the shell command. Guess that's what happens
when a newbie tries to program.

Thanks again
-----Original Message-----
I found the same problem runnning your script from a
VBS. After some
hacking I went into the registry he

HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\comman d

and renamed the Command key to Commandx so that
the "default" command was
used. After that the file opened from the script. Not
much of a solution I
know.

An alternative from a VBS is using automation:

Dim XL
Set XL = CreateObject("Excel.Application")
XL.Workbooks.Open "c:\Book1.xls", 3
XL.Visible = True

Whether this is a viable alternative for your purposes I
don't know.

--
Jim Rech
Excel MVP


.