I develop my code with the reference. But when I release it to others, I change
it late binding. I couldn't live without the intellisense, either.

And who knows about quitting the application? I figured that there wasn't
really enough code in that post to venture a guess (no saving, no closing, no
releasing other objects???).

Steve Gerrard wrote:

Dave Peterson wrote:
I should have been more explicit.

My point was since he was using this:

Set moExcelApp = CreateObject("Excel.Application")
instead of
Set moExcelApp = new Excel.application

why not just stick with late binding and drop the reference
completely and declare those variables as Objects?



He would lose intellisense, and have to look all the parameters up to be sure
they were correct, or wait for runtime errors. Also late binding all the calls
would slow the performance down quite a bit. The advantage of using create
object with Excel is that it is not version specific.

Back to the original post, shouldn't there be a
moExcelApp.Quit
before the
Set moExcelApp = Nothing
or is that not needed?

--

Dave Peterson