Bob

I agree it is debatable and particularly when only controlling Excel from
within itself, but with automation I find it essential. I once had a real
issue while trying to automate Outlook from Excel and failing to release the
variables left the process(es) open. This may have been version specific,
but find it always best practice, for the time it takes to explicitly
release object variables Just my £0.02 really

--
HTH
Nick Hodge
Microsoft MVP - Excel
Southampton, England
HIS


"Bob Phillips" wrote in message
...

"HeatherO" wrote in message
...
Thanks Nick. Like I told Bob I am slowly but surely starting to
understand
this a little. This is very different from RPG and stuff. So I just
have
to
set the reference once and then I can use those object variables as I
would
have if I had typed it using the excel library. I never thought of
clearing
the object variables at the end but that would be a good practice for me
to
do since it could cause problems.

It is debatable as to whether this is necessary. If you have finished with
an object and you have lots more work to do, no question it is a good
practice to release that resource, but at the end of an app?

I have been here before, and here is a little discussion between Dick
Kusleika and myself, that you can read at http://tinyurl.com/6gknq