It depends on the version of Excel and the service pack you are using. It has nothing to do with .Net in any way.
In other words, it was a known bug in certain versions/service packs of Office. So you need to go to support.microsoft.com and search for the solution.
Robert
At 12:00 AM 11/5/2004 -0500, you wrote:
Date: Thu, 4 Nov 2004 14:18:29 -0500 From: "Sinha, Amit (GE Energy, Non GE)" <[EMAIL PROTECTED]> Subject: Memory and Instance Issues in Excel Automation in Vb.Net
Hey, I am getting a weird problem in Excel Automation with VB.Net, and I will try my best to make you people understand the problem also hope somebody has something to say on that.
I have to populate some reports and data onto Excel file and for that I create the object of "Excel.Application" and couple of other objects and after the processing is done, I just need to show the excel on the screen for which I just say ObjExcel.Visible = True and after that free up my memory by stating every object as Nothing.
Here comes the problem, when the user closes the Excel App manually by clicking on X or Alt F4(what ever way) the instance of Excel.exe remains there in Task Manager in process windows and user has to forcefully kill the session by killing the process otherwise He/She will not be able to open other excel sheet on the same machine manually.
Hope I am able to make you people understand the problem. Any breakthrough will be highly appreciated..!!!
Thanks, Amit Sinha
=================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in:
Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet
View archives and manage your subscription(s) at http://discuss.develop.com
