Here is the problem:

I Have a vb 6 app that uses excel version 2003 in the code. Everything
works file on a desktop. However when running on a Windows 2000 Server in
the production environment it fails. I know the reason why, because excel is
not loaded on the production server. I'm getting pushback from the Windows
2000 Server box administrator about loading excel.exe on the production
server. This is preventing the automation of this job, and I was wondering
what details I could provide to the administrator to help sway his decision.

His arguement is that excel.exe is a desktop tool, and not to be loaded or
ran on the Windows 2000 Server box. Any talking points would be much
appreciated.
Thanks in advance.

these may be more talking points for the administrator:

http://support.microsoft.com/kb/257757/en-us
Considerations for server-side Automation of Office

--
Regards,
Tom Ogilvy


"thekichler" wrote:

Here is the problem:

I Have a vb 6 app that uses excel version 2003 in the code. Everything
works file on a desktop. However when running on a Windows 2000 Server in
the production environment it fails. I know the reason why, because excel is
not loaded on the production server. I'm getting pushback from the Windows
2000 Server box administrator about loading excel.exe on the production
server. This is preventing the automation of this job, and I was wondering
what details I could provide to the administrator to help sway his decision.

His arguement is that excel.exe is a desktop tool, and not to be loaded or
ran on the Windows 2000 Server box. Any talking points would be much
appreciated.
Thanks in advance.

Can the workbook files on the server be made available to the workstations?
Have the administrator make a network drive on the server that can be
accessed from your workstation.

You have to compare the cost of installing office on every desk top verses
the cost of installing office on the server. If everybody who is going to
use the workbook has Office and has access to the server (network drive) then
it doesn't make sense to install excel on the server.

"thekichler" wrote:

Here is the problem:

I Have a vb 6 app that uses excel version 2003 in the code. Everything
works file on a desktop. However when running on a Windows 2000 Server in
the production environment it fails. I know the reason why, because excel is
not loaded on the production server. I'm getting pushback from the Windows
2000 Server box administrator about loading excel.exe on the production
server. This is preventing the automation of this job, and I was wondering
what details I could provide to the administrator to help sway his decision.

His arguement is that excel.exe is a desktop tool, and not to be loaded or
ran on the Windows 2000 Server box. Any talking points would be much
appreciated.
Thanks in advance.