469,963 Members | 1,984 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,963 developers. It's quick & easy.

Starting and Quitting Excel

I've seen questions of how to check if Excel is already running.

If the user has already started Excel normally; call this Excel(User),
then vb.net code runs:
myXL = CreateObject("Excel.application")

Does this new instance of Excel(VB) work completely separate from the
Excel(User)? If yes, why is there a need to check if Excel is running?

When ending the Excel(VB), is there a way to quit this instance and
leave the Excel(User) instance if it's still active?

Thanks,
George
Nov 20 '05 #1
1 1492
* te*****@hotmail.com (George) scripsit:
I've seen questions of how to check if Excel is already running.

If the user has already started Excel normally; call this Excel(User),
then vb.net code runs:
myXL = CreateObject("Excel.application")

Does this new instance of Excel(VB) work completely separate from the
Excel(User)? If yes, why is there a need to check if Excel is running?
There is no need to check if excel is running.
When ending the Excel(VB), is there a way to quit this instance and
leave the Excel(User) instance if it's still active?


Did you have a look at the articles about Excel automation at the
Microsoft support site?

HOWTO: Automate Microsoft Excel from Visual Basic .NET
<http://support.microsoft.com/default.aspx?scid=kb;en-us;301982>

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>
Nov 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

By using this site, you agree to our Privacy Policy and Terms of Use.