StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPrevent Excel from quitting
primarykey
Id
3724301
data
AcceptedAnswerId
3813889
AnswerCount
6
ClosedDate
CommentCount
11
CommunityOwnedDate
CreationDate
2010-09-16T06:46:56.590
FavoriteCount
2
LastActivityDate
2011-04-06T14:33:16.820
LastEditDate
2011-04-06T14:33:16.820
LastEditorUserId
55787
OwnerUserId
55787
ParentId
0
PostTypeId
1
Score
12
ViewCount
2470
LastEditorDisplayName
text
Body
I'm missing an <code>Excel.Application.Quit</code> or an <code>Excel.Application.BeforeQuit</code> event. Does anybody know a workaround to mimic these events? I access Excel from a C# WinForms application via COM Interop. Given an <code>Excel.Application</code> object, how can I: <ol> <li>Preferrably prevent Excel from quitting?</li> <li>If this is not possible, how can I at least notice when Excel is quit?</li> </ol> Please note: Since I have a COM reference to the <code>Excel.Application</code>, the Excel process does not exit when Excel is "quit" by the user. Although this sounds contradictory, that's how it is. By "quit" I mean that the user hits "Quit" or the "cross button" at the top right corner of the window. The window closes, the files are unloaded, the add-ins are unloaded and whatever stuff Excel does apart from that which I have no clue of. But I can still use the <code>Application</code> object to "revive" the process and make Excel visible again, though the add-ins are then missing, and I have no certainty about what else is in an undefined state. To get rid of this problem, I would like to either Cancel the Quit at the very start (Think of a <code>BeforeQuit</code> <code>Cancel = true</code> if it existed), or at least be notified when Excel is quit, so I can release the COM objects and make the process really exit, and next time I need Excel again, I will know that I need to start it up first. Unfortunately it's a vicious circle: As long as Excel runs, I need the COM objects. So I can't dispose of them before Excel is quit. On the other hand, as long as the COM objects are there, the process doesn't exit even if Excel pretends to quit, so I cannot wait for a process exit event or similar. I have the unpleasing feeling that I'm going to bash my head against a brick wall...
Tags
<c#><excel><com><interop><excel-2007>
Title
Prevent Excel from quitting
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USchiccodoro
UserOwnerUserId
1. USchiccodoro
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPrevent Excel from quitting
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POPrevent Excel from quitting
 UserUserId
 USchiccodoro
 VoteTypeVoteTypeId
 VTBountyStart
3. VO
 singulars
 PostPostId
 POPrevent Excel from quitting
 UserUserId
 USHugh Allen
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.