Hi I use MFC Visual C++ 4.2.

I am automating Excel from my application.

My problem is I cannot quit the Excel after the automation process finished!

I checked it still exists on the Process lists and the most DANGEROUS is
everytime the automation function run, it create other Excel and so on. So it
must be out of memory soon.

I have used the app.Quit() method like all the people used but it DOES NOT
work.

What should I do?

Thank you.

Maybe you have not released other Excel objects (workbook, sheet etc) that
you may have set earlier, or thought you had but not in the right order
which should normally be done in reverse order as to how you set them.

Regards,
Peter T


"Landon" wrote in message
...
Hi I use MFC Visual C++ 4.2.

I am automating Excel from my application.

My problem is I cannot quit the Excel after the automation process
finished!

I checked it still exists on the Process lists and the most DANGEROUS is
everytime the automation function run, it create other Excel and so on. So
it
must be out of memory soon.

I have used the app.Quit() method like all the people used but it DOES NOT
work.

What should I do?

Thank you.

You might also need to destroy your "app" reference after doing app.Quit
unless it is due to fall out of scope naturally.

Peter T

"Peter T" <peter_t@discussions wrote in message
...
Maybe you have not released other Excel objects (workbook, sheet etc) that
you may have set earlier, or thought you had but not in the right order
which should normally be done in reverse order as to how you set them.

Regards,
Peter T


"Landon" wrote in message
...
Hi I use MFC Visual C++ 4.2.

I am automating Excel from my application.

My problem is I cannot quit the Excel after the automation process
finished!

I checked it still exists on the Process lists and the most DANGEROUS is
everytime the automation function run, it create other Excel and so on.
So it
must be out of memory soon.

I have used the app.Quit() method like all the people used but it DOES
NOT
work.

What should I do?

Thank you.

I have release the range and sheet like this:
　　　　　　　　// Release dispatch pointers.
range.ReleaseDispatch();
sheet.ReleaseDispatch();

book.Close( covTrue, covOptional, covOptional );
app.Quit();

1. Is this not enough? What should I add?
2. "You might also need to destroy your "app" reference after doing app.Quit "
How to do this? I think I haven't done the destroy step because I don't
know how and everybody just use the Quit().

Thank you.

I'm guessing about the syntax but based on how you released your other
objects maybe something like this -

book.Close( covTrue, covOptional, covOptional );
book.ReleaseDispatch();
app.Quit();
app.ReleaseDispatch();

BTW, is it OK to use a name like "app" in C++ to refer to the Excel object.
In say VB6 it would cause confusion as "app" is a keyword that refers
directly to the host dll or exe.

Regards,
Peter T


"Landon" wrote in message
...
I have release the range and sheet like this:
????????// Release dispatch pointers.
range.ReleaseDispatch();
sheet.ReleaseDispatch();

book.Close( covTrue, covOptional, covOptional );
app.Quit();

1. Is this not enough? What should I add?
2. "You might also need to destroy your "app" reference after doing
app.Quit "
How to do this? I think I haven't done the destroy step because I
don't
know how and everybody just use the Quit().

Thank you.

Pete, I have tried the steps you gave me but it did not changed anything.

It's ok in MFC to use app.

How to destroy the app reference according to your previous post? I think it
will solve my problem.

Thank you.

Hi I use MFC Visual C++ 4.2.

I am automating Excel from my application.

My problem is I cannot quit the Excel after the automation process
finished!

I checked it still exists on the Process lists and the most DANGEROUS is
everytime the automation function run, it create other Excel and so on.
So it
must be out of memory soon.

I have used the app.Quit() method like all the people used but it DOES
NOT
work.

What should I do?

Even I try to use the kill process but still no benifit

*** Sent via Developersdex http://www.developersdex.com ***

Ensure you release all references in the order created before, eg to
worksheet, workbook etc, then the release application reference after doing
..Quit

Another reason the instance may remain open is if any user dialogs are open
pending a response, eg "do you want to save...". Until you have sorted
things out make the instance visible before closing it. If you can't then
close it manually that'll confirm you still have a reference attached.

Regards,
Peter T

"Hardik Soni" wrote in message
...


Hi I use MFC Visual C++ 4.2.

I am automating Excel from my application.

My problem is I cannot quit the Excel after the automation process
finished!

I checked it still exists on the Process lists and the most DANGEROUS is
everytime the automation function run, it create other Excel and so on.
So it
must be out of memory soon.

I have used the app.Quit() method like all the people used but it DOES
NOT
work.

What should I do?

Even I try to use the kill process but still no benifit

*** Sent via Developersdex http://www.developersdex.com ***