Adding a Spreadsheet to the Front Panel

[albertm]

Hi,

The example you posted on 7-31-2006 to this thread has the problem.  Just start it and open the task manager and watch the memory go up and up on LabVIEW.  If you use a big range and a shorter delay then it goes up quickly.  You might want to save everything before you push it because funny things may happen.

I'll really miss the formatting and the ability to lock certain cells if I can't use the spreadsheet.

Thanks,

Albert

[Joe_H]

I just got done running this vi continuously overnight with a range of A1:a65536 to c1:c65536 with all item full and I did not see any memory leak. Pls post your vi, also what version of LV are you using.

[albertm]

Hi,

I simplified and attached my VI that has the problem.  It seems as though the problem is caused by some interaction between arrays and the spreadsheet stuff.  If you run my VI as it is there isn't a problem but if you remove the Conditional Disable structure then you'll see the problem.  I also tried auto-indexing the string but the same thing happened.

I'm running LabVIEW 8.01.

I thought I saw the same problem with your VI because I ran it and saw the memory usage creeping up but I didn't wait long enough because it basically went up and down and I didn't look at it after I stopped it.

Thanks a lot,

Albert

[Joe_H]

Albert,

this kind of puzzles me because I do not see any increase of memory usage at all with the vi that you supplied . Do you still get an out of memory crash.

very wierd, it could be just different PC's or versions of win"dose" or a different excel object. Who knows. 

[albertm]

Hi,

Did you remove the Conditional Disable structure and try it?

It happens to me at home (XP Pro) and two computers at work (XP Pro & Media Center).

By the way, I set it up this way because I was using the Text property as opposed to the Value2 property because Text is formatted according to the spreadsheet.

Thanks,

Albert

Message Edited by albertm on 08-25-2006 01:35 PM

[Joe_H]

yes I did remove the structure and try it with the same results. I am have winXP pro p4 3.2GHz with 1gig Ram.

[albertm]

Hi,

I wonder if crying would help.  Actually, do you have any suggestions for troubleshooting this?  I guess I'm being stubborn by not using a table at this point.

Thanks,
Albert

[albertm]

Hi,

I fixed the problem by using the function "Close Reference" after I'm done with each ActiveX reference (especially those in loops).  My friendly neighborhood NI salesman figured it out; NI's support service didn't even come up with this!

Albert