>Hmmm...I've been using Office2000 routinely under Win98SE and Win NT 4.0 SP5 and haven't seen that one. I usually do an oExcel.Quit() AND oExcel = .NULL.
>
>Now screwing around with this on my laptop with Win NT4 SP5 I see that EXCEL.EXE stays in the Task Manager (is it a Tasker Manager on your machine?) after an oExcel.Quit but it goes away with oExcel = .NULL.
>
>Hmmm.....try using both?
Well, I'm still not certain what's causing this on my machine at work. I haven't been able to replicate it here at the house. However, there is some strange flashing that occurs when when the server is released.

About the only thing that I can think of that might cause this is that when the variable is set to NULL, for some reason, the destructor releases the property that holds the reference to the server isn't being called. Why? Beats me, but it is happening. I assume that there's some difference between what I'm doing here and at the office. Perhaps I need to do a re-install at the office.

At any rate, the first thing I'll try is setting the server reference to NULL in the parent class.

Thanks to all for their input, and happy holidays to all.