As far as I've seen it has been caused by errors in either the .Net
Framework/Interop or people's code.
As such, it's not an Excel issue, but more that .Net's COM implementation is
not good.

NickHK

"Sriram" wrote in message
...
Hi,
I wonder if the excel.exe staying in memory when excel is automated via
..net
is resolved in Excel 2007 or does it still persist?

Thanks
Sriram