Hello;

I've done a VB program that opens an Excel Sheet Object
and writes some data into it from Access. It works fine
when I activate the .cmd file that starts the program, but
if I automate it by means of the build-in MS scheduler, it
gets an error when the program does "Set objexcel =
CreateObject("Excel.Sheet")". I should add that I only get
this error when running on a server. The program can run
under scheduler control on my own labtop without problems.
I use the same user ID on the server and in the Scheduled
Task (Run as: <user ID.)

Thank you for any help.

Regards Peter Hoyler

The object can only be created IF excel is
installed...and I'd be surprised if your server had excel
installed - most IT depts don't allow progs to run on
remote servers as there's too much risk involved.

-----Original Message-----
Hello;

I've done a VB program that opens an Excel Sheet Object
and writes some data into it from Access. It works fine
when I activate the .cmd file that starts the program,
but
if I automate it by means of the build-in MS scheduler,
it
gets an error when the program does "Set objexcel =
CreateObject("Excel.Sheet")". I should add that I only
get
this error when running on a server. The program can run
under scheduler control on my own labtop without
problems.
I use the same user ID on the server and in the
Scheduled
Task (Run as: <user ID.)

Thank you for any help.

Regards Peter Hoyler
.

Thanks for the answer, but Excel is installed. In fact it
works fine as long as I don't use the scheduler. If I sign
on to the server by MS Terminal Client and dubbel-click
the .cmd file that starts the program, it runs fine. But
when I run the .cmd file through the scheduler, I get the
error. Both ways works ok on my labtop.

regards peter

regards peter
-----Original Message-----
The object can only be created IF excel is
installed...and I'd be surprised if your server had excel
installed - most IT depts don't allow progs to run on
remote servers as there's too much risk involved.

-----Original Message-----
Hello;

I've done a VB program that opens an Excel Sheet Object
and writes some data into it from Access. It works fine
when I activate the .cmd file that starts the program,
but
if I automate it by means of the build-in MS scheduler,
it
gets an error when the program does "Set objexcel =
CreateObject("Excel.Sheet")". I should add that I only
get
this error when running on a server. The program can run
under scheduler control on my own labtop without
problems.
I use the same user ID on the server and in the
Scheduled
Task (Run as: <user ID.)

Thank you for any help.

Regards Peter Hoyler
.

.