Releasing Memory 2

[spats]

I'm using quite a bit of VBA code in a excel spreadsheet, and everytime the code executes, memeory usage goes up by about 100K, according to Task Manager. This memory is never released, and available memory just becomes less and less with each execution. Is there some procedure I can write at the end of my code to release the memory?

 

[CajunCenturion]

That will depend on what you're doing, and where in the VBA code you're doing it. Most likely, you're allocating memory for dynamic objects but not release those objects when you're done. Have you narrowed things down to one or more specific sections of code, and if so, what are you doing in those sections?


Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[spats]

The code is full of altering and filling in cell ranges. Sometimes individual cells, sometimes cell groups. I know that a range of cells is considered an object in vb’s eyes, but i have not named each object individually. I am hoping there is a general way to release ram when procedure is complete.

 

[atook]

When writing VB code, it's a good idea to release all of your objects by setting them to nothing. It's less important with variables decalared as strings, or other types, but application objects should be set to nothing. i.e.:

dim objRange as Excel.Range

blah blah magic code blah.

' we're done with the range, so clean up.
set objRange = Nothing\



Tim Grote - The Irrigation Engineers.

http://www.irrigationengineers.com

 

[yakpol]

Check if you have globally declared arrays or objects. They will not dissappear when code execution is over. Clean up at the end of routine:
Erase MyArray()
Set MyObject = Nothing

But it could be some of Excel problems as well.