[AccessD] Excel object behavior

Don,

I'm not sure I understand what is the issue? - if you tell that "the
instance DOES go away" but in the same time you tell that you're
"overlooking a pointer somewhere that needs to be set to Nothing."...

I mean if MS Excel instance does go away - that's OK IMO, and everybody
should be happy even without setting all the pointers to nothing :)...

What am I missing?

Thank you.

--
Shamil

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of McGillivray, Don
[IT]
Sent: Wednesday, September 24, 2008 7:46 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Excel object behavior

Shamil,

Thanks for the detailed explanation.  And yes, I was watching the processes
tab of the task manager.  I was careful to make sure that there were no
Excel instances present before running the procedure.  As I step through the
part of the code that cleans up (closing workbooks, quitting Excel, setting
pointers to Nothing, etc.) the instance remains on the processes list.  Only
upon execution of the "Exit Function" line of the procedure does the
instance disappear - but the instance DOES go away, it doesn't remain a
ghost.

I suspect that I'm overlooking a pointer somewhere that needs to be set to
Nothing.  I thought I got them all, but maybe not . . .

Don