Specify Excel Version in Task Scheduler (Excel 2000/2003)

Topic

New Reply

Task supposed to run daily refuses to run now that Excel 2003 has been installed.
Versions of Excel in different locations running fine otherwise.
.cmd file simply opens an Excel file which runs code in its Open Event.
.cmd file executes flawlessly when typed into the Start/Run box.
Macro security set to Low.
Does anyone have any ideas?

Reply | Quote

Replies

I don’t complete understand what is not working.

From what I understand, the scheduler opens excel and an excel file and the file runs its workbook open code. What else do you want to happen?

Steve

Reply | Quote

Steve,
The scheduler was opening the file but no longer does.
Ross

Reply | Quote

In the scheduler, insert the complete path to the Excel version you need, followed by the path and filename of the file to open, e.g.:

“c:program filesmicrosoft office 2003office11excel.exe” “c:databook1.xls”

Reply | Quote

Jan Karel,
Adding the path to the program seemed like the answer, and I am pleased to now know how to programmatically choose the version of Excel I’d like to run, but it still refuses to run from the scheduler. Ok in the Run box, but when I right-click on the item in the scheduler it just stares back at me
Ross

Reply | Quote

To all those who puzzled over this post: The task scheduler is a neat tool, but when day after day it does what you want without fail, you might forget about it. I did, until one day I decided to check and saw that it had not performed for OVER A MONTH. Luckily, the task was not critical, but what if it had been? I thought it went off the rails because at about that time (yes, a log of changes would have nailed the time!) I installed an extra version of Excel. What I forgot was that I had changed my password. How did I find out? By looking (finally) at the scheduler’s log, silly. There are several lessons here for me, maybe for others too.

Reply | Quote

>you might forget about it

Given that it takes a minimum of 4 clicks to access any Task – unless you build the entire Tasks folder into QuickLaunch – forgetting about it is tempting.

Reply | Quote