I'm hoping someone can help here. I've been working on a project that requires data exports to Excel spreadsheets. I've done this successfully in InterDev w/a COM component built in VB6, and have migrated both the webpage and COM into VS.Net. The problem is that when the code is finished, Excel.EXE is still running - despite calling the Quit() method.

I am using Excel 2000 right now and have not updated to Office 2003 as of yet. This simple code example causes this:

Private Sub RunExcelCheck()

   Dim objExcel As New Excel.Application()

   System.Threading.Thread.Sleep(10000) 'So I can see the .exe file running

   objExcel.Quit()
   objExcel = Nothing

End Sub

Help! This is the last piece to a successful migration!

MG

Try changing the line :

objExcel = Nothing

to :

set objExcel = Nothing

This is the only difference I could see between it and the MS descriptions.

Set objExcel = Nothing does not work in VB.Net code - the "Set" is implied.

Thanks anyway!

MG

I found the answer:

http://support.microsoft.com/default...b;EN-US;317109

It works but now I have to find the offending object which is buried
in code. Oh happy joy joy.

MG