Excel created by AutoIt does not fully quit

[jnash67]

I am creating an excel instance and waiting for it to close. However, when the excel quits through either the file menu or through an application.quit VBA call, the window disappears but it doesn't really die. In the following code I never get to the msgbox until I actually kill the process with process manager.

Local $oe = _ExcelBookNew()
$oe.caption = "123"
WinWaitClose("123")
MsgBox(0, "bye", "bye")
Exit

I haven't found any way to get Excel to actually fully die. How can I get this to happen?

[GEOSoft]

You might be better off with

ProcessWaitClose()

[Juvigy]

Check those out:

$oExcel.Workbooks.Close

$oExcel.Application.Quit

[jnash67]

Check those out:

$oExcel.Workbooks.Close

$oExcel.Application.Quit

ProcessWaitClose has the same problem as WinWaitClose. It's not closing -- neither the window or the process. So the below code never gets to the Msgbox either:

Local $oe = _ExcelBookNew()
$oe.caption = "123"
Local $oep = WinGetProcess("123")
ProcessWaitClose($oep)
MsgBox(0, "bye", "bye")
Exit

For $oExcel.Workbooks.Close and $oExcel.Application.Quit, I know I can kill Excel from AutoIt. The issue is, I need AutoIt to wait until the user kills Excel. However, even when the user kills Excel, it doesn't really die. The window and process are still there in some form or another, although the excel window in the UI seems to have disappeared.

[l3ill]

This is a bug (at least in my opinion) if you hold down the shift when closing it should kill it off good

[water]

I had a similar problem when running the 32 bit version of Office on a 64 bit operating system (Windows 7) and executing/compiling the script for 64 bit.

When compiling the script for 32 bit everything was running fine again.

[jnash67]

The solution to this issue is for AutoIt to release the object variable as follows:

Local $oe = _ExcelBookNew() 
$oe.caption = "123" 
$oe = 0 ; this releases the object
WinWaitClose("123") 
MsgBox(0, "bye", "bye") 
Exit

If you store the HWND or PID before releasing (with WinGetHandle or WinGetProcess), you can retrieve the object using WinAPI functions like _WinAPI_Getwindow.

I would still consider this a "bug" because the AutoIt documentation says you no longer need to release objects (although this is in reference to memory management).

Edited September 24, 2010 by jnash67

[jnash67]

I had a similar problem when running the 32 bit version of Office on a 64 bit operating system (Windows 7) and executing/compiling the script for 64 bit.

When compiling the script for 32 bit everything was running fine again.

Everything I did was in a 32-bit environment