VBE windows, zoom, ActiveX controls: Just one hit on memory, or many?
WHA
as "Memory Problem: Have I hit the 64K boundary?" and "Memory problem:
Out of Memory and cannot save." I have a new observation and a couple
more questions.
The observation: When I minimize the Excel main and VBE windows, the
"Mem Usage" reported for EXCEL.EXE in Task Manager goes down from
20-40MB to under 5MB. Granted, when I un-minimize these windows, the
memory usage goes back up, but it is interesting. Does it say anything
about my problem?
My main question, though, is about some of the usual suspects I've
heard about with regard to memory consumption: Leaving many VBE
windows open; having a Zoom other than 100%; and putting ActiveX
controls on worksheets. I've done each of these and expected that they
would each inflict a temporary or one-time boost in memory
consumption. But could it be that, over time, these issues eat up more
and more memory?
If the answer to that last question is Yes, would you recommend that I
move all my ActiveX controls (about 5 on the "home" worksheet, 20 on
another worksheet) into UserForms and ask the users to keep the Zoom
at 100? I hope this is not necessary...
Thanks in advance, WHA
Background: I am building a VBA-based tool in Excel 2003 on Windows
XP. I'm having some kind of memory leak problem: I get "Out of
memory," with no mention of Error 7. This can occur simply when I am
in the VBE without any of my code running. Also, after the error
occurs, I am unable to save the workbook, even to a local drive. This
is the fifth of four -- err, five -- posts with questions about what
the source of this error might be.
FACTS (updated with some more info). I am using:
MS Office Excel 2003, SP3
MS XP Professional Version 2002, Service Pack 2
Dell Inspiron 9400; Intel Core2 CPU; T7...@2.00GHz; 998MHz, 2.00GB of
RAM
"Total paging file size for all drives: 2046 MB" in System Properties/
Performance Options
Less than 600MB of PF Usage in Task Manager
My Excel workbook is about 2MB in size. It goes down to about 1.5MB
when I run Code Cleaner.
When the memory error occurred recently, EXCEL.EXE was taking up about
55MB of memory (according to Windows Task Manager).
Preliminary measuring of =INFO("memused") seems to show 1.2MB when
tool is first loaded, then to fluctuate between 2 and 3 MB. (I did not
test this when the memory error occurred.)