Activex Excel Automation: the Missing Handle

[LVSteve]

Further testing on a different machine has shown that the exact code in labview 7.1 works correctly.  Which explains why it hasn't been a problem in almost 10 years.

[nyc_(is_out_of_here)]

---

@LVSteve wrote:

Further testing on a different machine has shown that the exact code in labview 7.1 works correctly.  Which explains why it hasn't been a problem in almost 10 years.

---

Same exact code in LabVIEW 7.1 and Excel 2007?

[LVSteve]

---

@nyc_(is_out_of_here) wrote:

---

@LVSteve wrote:

Testing on my coworker's computer has revealed on Win7 you don't need to have *any* close references, and the excel.exe process will still stop running after the VI finishes, although you have to wait 10-15 seconds.

Here is the latest VI

---

Remove the Workbook.Save and move the Workbook.SaveAs to its place.

---

Done.  I'm afraid it still doesn't work.

[ben64]

This KB might give some hint, it seems that this behavior is by design. Althought we don't get the errors described in the kb it precised that to avoid errand references the code should be modified to call a qualified Excel object.

http://support.microsoft.com/kb/178510/en-us

Ben64

[LVSteve]

Yes, I have the source in LV7.1 from 2004.

I have a test PC with LV7.1 and office 2007 for occasions like this 😃

[LVSteve]

---

@ben64 wrote:

This KB might give some hint, it seems that this behavior is by design. Althought we don't get the errors described in the kb it precised that to avoid errand references the code should be modified to call a qualified Excel object.

http://support.microsoft.com/kb/178510/en-us

Ben64

---

Would it help if I did something like select a different worksheet before I tried to get the workbook.activesheet reference?  That's the line of thinking that George has been hinting at, and I've explored this afternoon to no avail.

[nyc_(is_out_of_here)]

---

@LVSteve wrote:

---

@nyc_(is_out_of_here) wrote:

---

@LVSteve wrote:

Testing on my coworker's computer has revealed on Win7 you don't need to have *any* close references, and the excel.exe process will still stop running after the VI finishes, although you have to wait 10-15 seconds.

Here is the latest VI

---

Remove the Workbook.Save and move the Workbook.SaveAs to its place.

---

Done.  I'm afraid it still doesn't work.

---

Your VI works for me on my laptop. Windows 7 Pro, LV 2010SP1, Excel 2010

Edit: Nevermind.  There Excel is still running in the background.

[LVSteve]

If anyone has labview 7.1, you can run the first piece of code and see that it works with no problems.

The second is simply the same VI recompiled in LV2009 and it does not work, because excel.exe is left running.

Can anyone from NI weigh in on this?

[Ajay_MV]

Hellow Arc.g,

It's been year since you posted this bug of LV and I'm facing the same issue now and want to stop the EXCEL.EXE process properly (i.e., without any harst stopping using command line as posted in other thread here).  Have you ever found out a way to solve this?  

I have also narrowed down to the place where ActiveWorksheet property node is causing this problem before visiting this page B-)

Thanks,

Ajay.

[Blizzard]

Hi Ajay,

I hope you are doing well.

I am assuming you don't want to use CONTROL>ALT>DEL either to stop Excel either? 

Also, I would post this question as a new issue so that it will be active for others to see and feedback on.

Best Regards,

Anna L