oExcel:Quit()

[Rick Lipkin]

To All

I use Ole to create excel files and when I finish .. I always close Excel with oExcel:Quit() .. unfortunately if I open the task manager I still see Excel running as an open task. When I quit my application .. the Excel task closes.

What am I missing to make sure Excel close and not linger as an open process?

Thanks
Rick Lipkin

[cnavarro]

Try

oBook:Close()
oExcel:Quit()
oExcel := Nil

[ukoenig]

Another solution forces EXCEL to be closed ( or define any other app )

WINEXEC( "taskkill /F /IM EXCEL.EXE"

call taskkill /? to get the parameters

regards
Uwe

[Gale FORd]

One of the problems is If there is an Excel error or prompt you might loose control of the excel connection.
Sometime I turn on the visibility so I can see if there are any messages from Excel program.
Also before trying to create a file from excel, I have started checking for the (.xlsx) files existence and deleting it .
That way if i cannot delete it I know it is still open from a prior or current Excel session. It's things like that makes it harder to automate ole tasks.

[cnavarro]

Please,

viewtopic.php?f=22&t=32928

[Enrico Maria Giordano]

To All

I use Ole to create excel files and when I finish .. I always close Excel with oExcel:Quit() .. unfortunately if I open the task manager I still see Excel running as an open task. When I quit my application .. the Excel task closes.

What am I missing to make sure Excel close and not linger as an open process?

Thanks
Rick Lipkin

Can I see a sample (better if compilable and runnable) of your code?

EMG

[nageswaragunupudi]

Try

oBook:Close()
oExcel:Quit()
oExcel := Nil

Mr Cristobal's advice works for me.
After oExcel := nil, the excel goes out of memory.

[Enrico Maria Giordano]

Try

oBook:Close()
oExcel:Quit()
oExcel := Nil

Mr Cristobal's advice works for me.
After oExcel := nil, the excel goes out of memory.

It is only needed if oExcel is a static, public or private variable. I recommend to use a local variable instead.

EMG

[cnavarro]

Enrico, Please, you can put a small example using a local variable?

[Enrico Maria Giordano]

Here it is:

Code: Select all  Expand view

#include "Fivewin.ch"


FUNCTION MAIN()

    LOCAL oExcel, oSheet

    oExcel = CREATEOBJECT( "Excel.Application" )

    oExcel:WorkBooks:Add()

    oSheet = oExcel:ActiveSheet

    oSheet:Cells( 1, 1 ):Value = "This is a test"

    oSheet:SaveAs( CURDRIVE() + ":\" + CURDIR() + "\ThisIsATest.xlsx" )

    oExcel:Quit()

    RETURN NIL

EMG

[cnavarro]

Ah !, Ok, I understand, only in the event that Excel does not remain open

[Rick Lipkin]

To All

I have been updating some old code especially where all variables are defined Static at the top of the reports .. part of the code upgrade was to remove all the Statics and use Local's instead. In many cases oExcel was not defined at all ( as in this case ) .. Once I re-defined oExcel and oSheet as local to my Excel file extraction, Excel now un-loads from memory with oExcel:Quit()

Sorry for such a stupid error, however .. I now will go back and look at all my reports and make sure the Static to Local variable conversion makes sure oExcel and oSheet are defined and defined Local to each report module.

Thanks for everyone's input ..

Rick Lipkin