Labview does not release the memory used in Excel, even after Active X "Excel close file" AND close automation is executed.

[LVLJ]

Memory is only released after the VI is exited (via quit button) OR I kill the process in NT (with the VI still running). It is creating mega memory problems when opening and closing multiple large excel docs to extract cell values. Help.
Thanks.
LJ

[Gorka Larrea]

Check all your activeX references, and close them when you do not need them, and of course, quit Excel after you finish, else, instead of being invisible, it is in memory. If these all fails, check for errors in the error cluster after each operation, and if all this fails... well you could attach an example of your problem to see if I can recreate and solve the problem.

[Mark A. Hanning-Lee]

Gorka Larrea wrote:
>
> Check all your activeX references, and close them when you do not need
> them, and of course, quit Excel after you finish, else, instead of
> being invisible, it is in memory. If these all fails, check for errors
> in the error cluster after each operation

I noticed the same problem & tried all those ideas.

Even after your LV code tells Excel to quit, it stays in memory. (You
can see that in Task Manager.) It is only closed when your VI stops
running, or your application quits. NI tech support confirmed that as a
bug & told R&D.

At least, that is true with LV 5.1 & Excel 2000 SR-1; I haven't tried
other versions.

Mark

[Gorka Larrea]

Well, thanks to god (or NI?) that doesen't happen under LV 5.0.1f1 & Excel 97. Good luck.

[LBoltzmann]

This behavior is seen when you use the Invoke node Item/Index. In this case Excel won't exit.

[Mark A. Hanning-Lee]

Jeff M. wrote:
>
> This behavior is seen when you use the Invoke node Item/Index. In
> this case Excel won't exit.

Thanks. So how would you recommend making Excel exit?

Best, Mark

[Gorka Larrea]

Jeff, don't know what version of LV you are using, but in 5.0.1f1 THAT is not true, I think some time ago I had some problem like that, but the problem was the value I was passing to item/index was not adecuate, and the error cluster made the exit function not to execute. Try checking the value passed to item/index in highlight mode.

[Zhichao Chen]

Make sure you have closed every reference
you created. As long as there is one reference isn't closed, the excel will not exit. There is the same problem in the example of LabVIEW.
If you can upload the file, I can check for you.

[Grant_C]

I am seeing this LabVIEW problem in v2010.  Running a simple vi that opens an Excel report and then 'dispose report' will open and close Excel as you would expect but the Excel.exe remains in my task manager until i close down LabVIEW completely?

I attach the simple .vi

[stefan_hartmann]

Spoiler

i recognize the same problem with Labview2011.

es far as i see it has to do something with multiple times using item/index property node or something in this region.

cheers