Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspx_professional thread: Excel.EXE process stays in memory?


Message #1 by "Saul Kaplan" <kaplan@n...> on Wed, 20 Feb 2002 14:10:51
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1BB63.655B6750
Content-Type: text/plain;
	charset="ISO-8859-1"

Hi Saul,

For the Webclass, it was very specific for a project in scientometry.

I look your code, and I think you have to close your workbook object before
putting nothing:

        oWb.Save()
        oWB.Saved=True
        '........
        ' Make sure that we release object references.
	  oWB.Close()
        oXL.Quit()
        oWB = Nothing
        oXL = Nothing

Try it and give me news about that.

-------------------------------------------------
Francois Vallieres
Observatoire des Sciences et des Technologies
http://www.ost.qc.ca


-----Original Message-----
From: Saul Kaplan [mailto:kaplan@n...] 
Sent: Thursday, February 21, 2002 9:28 AM
To: ASPX_Professional
Subject: [aspx_professional] RE: Excel.EXE process stays in memory?

Hi Francois 

Thanks for your help.  I have waited for some time and the Excel instances 
remain in memory?  This is the .Net test code I am using, do you see any 
problems?  Your VB Webclass sounds interesting, do you think it can solve 
my problem?

Regards
Saul

Private Sub SalesPivotTable(ByVal sFileName As String)
        Dim oXL As Excel.Application
        Dim oWB As Excel.Workbook
        ' Start Excel and get Application object.
        oXL = CreateObject("Excel.Application")
        oXL.Visible = False
        oWB = oXL.Workbooks.Open(sFileName)
        '........
        oWb.Save()
        oWB.Saved=True
        '........
        ' Make sure that we release object references.
        oWB = Nothing
        oXL.Quit()
        oXL = Nothing
End Sub


$subst('Email.Unsub').


  Return to Index