Skip to Content
author's profile photo Former Member
Former Member

Excel still running after OLE program ends

I've spent all day on this and am getting nowhere, so it's time to turn it over to the experts here.

Env: WAS640

I have a very simple ABAP program that does some OLE with Excel. When the program is finished, EXCEL.EXE is still running on the PC (can see in task manager). After running the program 4 times, EXCEL.EXE shows up four times in the task manager.

I'm using FREE OBJECT on every OLE object, I'm FLUSHING... I don't get it. This does not happen in our old 620 system, on which we still run some apps.

One other oddity. When I debug my wrapup code...

SET PROPERTY OF excel 'DisplayAlerts' = 0.

CALL METHOD OF workbooks 'CLOSE'.

SET PROPERTY OF excel 'VISIBLE' = 1.

CALL METHOD OF excel 'QUIT'.

FREE OBJECT workbook.

FREE OBJECT workbooks.

FREE OBJECT excel. "Excel.Application

... and get to the 3rd line, Excel pops up on my screen and I can see that the workbooks are closed properly. But when I step through the 'QUIT' method, the application doesn't shut down, and I can still see the icon in my taskbar. Not sure if it's supposed to disappear at that point or not.

Whwn I free the excel object, the icon disappears, but the process is still alive in task manager.

Any ideas?

Thanks

Chris

Message was edited by: Chris Perkins

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Nov 22, 2004 at 07:13 AM

    Hi Chris,

    see oss-note 124658

    and here:

    http://www.abapforum.com/forum/viewtopic.php?t=693&highlight=free+excel

    Andreas

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Well, I've already done everything in note 124658 (and 129994 and 721793)... as I mentioned in my original post, all objects are freed (and the code works fine in a 620 environment). I've also made the Excel session visible, and don't see anything unusual going on that would explain the persistent thread.

      I've gotten around it for now by writing a call to a batch file that issues a taskkill command to the Excel process, but I was hoping for something a little cleaner.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.