Peter,

Yes, looked there, tried that. Didn't fix it.

My guess is that there is a policy enforced (this is a high security
facility) that might be adding an additional thread to Excel. Something that
works fine with excel normally, but is conflicting with Excel when used via
COM.

Would this be the right forum to expand on the issue or is there a better
forum to do so?

Thanks,

JustMe


"Peter T" wrote:

The difficulty of releasing Excel in .Net seems to crop up regularly (not
that I know much about it!)

See
System.Runtime.InteropServices.Marshal.ReleaseComO bject
and
GC.Collect()
in this article
http://support.microsoft.com/kb/317109

Typically ReleaseComObject is wrapped up in a function, plenty of examples
'out there'

Regards,
Peter T

PS I like the conspiracy theory though!


"JustMe" wrote in message
...
Hi all,

I have been over at the MSDN forums and someone pointed me here.

I am trying to create an instance of Excel from within .NET so I can
populate it with some data and save it. All works fine. However, after I
tell excel to quit (which it appears to do), if I go into task manager, I
can
see it is still running. And if I do the process again, I get 2 copies of
Excel in task manager. This is with Excel 2007 and Win XP.

I have tried a bunch of things, none of which have worked.

One possibility is that I work in at a defense contractor and it might be
that they have some policy or other behind the scene add on that might be
keeping Excel from exiting properly.

Anyway, I am hoping that there is a forum here where someone might have
some
ideas as to what might be keeping Excel from completely closing as it
should.
If so, could you point me in the correct direction?

Yes, I can provide much more details once I find the appropriate place to
discuss it.

Thank you,

JustMe



.