Hi Harald,

Bob's the name :-).

I have also seen mentioned, though not experienced it myself, that having
the app visible sometimes leads to the Quit not working (this may be in a
..Net environment now that I say it). The suggestion here was to make not
visible before the quit.

Bob


"Harald Staff" wrote in message
...
Hi RP

That depends on how well written the code is. If Excel asks to save
changes
or not, or something else that she may ask on quit, then it needs user
interaction. And if xlApp.Visible = True is not part of the show, then the
question will remain invisible and unanswered and the process will not be
terminated.

Best wishes Harald

"Bob Phillips" skrev i melding
...
The other thing I should have said is that if you create an application
object for the Excel App that you create, you can just quit that

xlApp.Quit

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Mike Moore" wrote in message
...
Could anyone provide ideas on how to kill an excel process? In our VB
6.0
app we populate data from MS Access to an MS Excel worksheet. If you
look
in
task manager you could see the excel processes running in the
background.
Also, how could we identify which excel process to kill? Especially
in
the
case where a user is working on an ms excel worksheet and then
generates
one
from our app. We don't want to kill the one the user is working on.
Only
the one we create from the app.