R
Robert
Has anyone encountered this problem. We have a VBA
command: Set xlApp = New Excel.Application. T
This command is in an application that will stay up and
running. The command above creates a new Excell
application, no problem there. The program will then go
about the task of creating a nice report. Once the report
is created however Excel is still running as a process as
seen in the Task Manager. Now if a user goes to Outlook
to read email and attempts to open an attachment that is
itself an Excel spreadsheet Outlook will hang and not
open the attachment. The only way to have Outlook open
the attachment is to end the program that created the
previous Excel process from the command above.
But, I can open many emails with all types of Excell
attachments thereafter, creating numerous running
instances of Excell without Outlook hanging.
Is this a VB issue or an Outlook issue with an Excel
process instantiated by VB?
Thanks!
Robert
command: Set xlApp = New Excel.Application. T
This command is in an application that will stay up and
running. The command above creates a new Excell
application, no problem there. The program will then go
about the task of creating a nice report. Once the report
is created however Excel is still running as a process as
seen in the Task Manager. Now if a user goes to Outlook
to read email and attempts to open an attachment that is
itself an Excel spreadsheet Outlook will hang and not
open the attachment. The only way to have Outlook open
the attachment is to end the program that created the
previous Excel process from the command above.
But, I can open many emails with all types of Excell
attachments thereafter, creating numerous running
instances of Excell without Outlook hanging.
Is this a VB issue or an Outlook issue with an Excel
process instantiated by VB?
Thanks!
Robert