I imagine this is a question about housekeeping more than anything else,
but...

A friend told me that in VB and some other languages that when a macro or
script ends, that it doesn't release the memory held by object variables,
and that one has to "clean up the garbage" before closing the program. Is
Excel no exception? If I use a large amount of object variables in my
application, should I reset them before closing?

If anyone can decipher what I'm saying and say it better, by all means
please do. lol

-gk-

"Set <object = Nothing"

--
Regards;
Rob
------------------------------------------------------------------------
"TBA" wrote in message
...
I imagine this is a question about housekeeping more than anything
else,
but...

A friend told me that in VB and some other languages that when a macro
or
script ends, that it doesn't release the memory held by object
variables,
and that one has to "clean up the garbage" before closing the program.
Is
Excel no exception? If I use a large amount of object variables in my
application, should I reset them before closing?

If anyone can decipher what I'm saying and say it better, by all means
please do. lol

-gk-

TBA,

There's a lot of good information and links here regarding memory in Excel:
http://www.decisionmodels.com/memlimits.htm

John

"TBA" wrote in message
...
I imagine this is a question about housekeeping more than anything else,
but...

A friend told me that in VB and some other languages that when a macro or
script ends, that it doesn't release the memory held by object variables,
and that one has to "clean up the garbage" before closing the program. Is
Excel no exception? If I use a large amount of object variables in my
application, should I reset them before closing?

If anyone can decipher what I'm saying and say it better, by all means
please do. lol

-gk-