Please Note: This article is written for users of the following Microsoft Excel versions: 2007, 2010, and 2013. If you are using an earlier version (Excel 2003 or earlier), this tip may not work for you. For a version of this tip written specifically for earlier versions of Excel, click here: Finding Other Instances of Excel in a Macro.
Written by Allen Wyatt (last updated April 22, 2024)
This tip applies to Excel 2007, 2010, and 2013
If you run a VBA program from within a particular instance of Excel, you can create other instances of Excel, open and modify workbooks in the newly created instances, and then close those instances. However, you may wonder how you can determine, within a macro, if other instances of Excel are already running, and, if so, take control of those instances.
There are a few ways you can go about doing this. If you simply want to know how many instances of Excel are running, you can use a macro that makes use of the Windows API. The following function implements this approach:
Public Declare Function GetDesktopWindow Lib "user32" () As Long Public Declare Function FindWindowEx Lib "user32" Alias _ "FindWindowExA" (ByVal hWnd1 As Long, ByVal hWnd2 As Long, ByVal lpsz1 As String, ByVal lpsz2 As String) As Long Function ExcelInstances() As Long Dim hWndDesk As Long Dim hWndXL As Long 'Get a handle to the desktop hWndDesk = GetDesktopWindow Do 'Get the next Excel window hWndXL = FindWindowEx(GetDesktopWindow, hWndXL, _ "XLMAIN", vbNullString) 'If we got one, increment the count If hWndXL > 0 Then ExcelInstances = ExcelInstances + 1 End If 'Loop until we've found them all Loop Until hWndXL = 0 End Function
This code was developed by Excel MVP Stephen Bullen and can be found at this site:
http://www.officekb.com/Uwe/Forum.aspx/excel-prog/55941
This, obviously, won't allow you access to the individual instances of Excel; it only returns a count of the number of instances open. If you want to develop code to use the instances, then you don't need to rely upon the Windows API. You can, instead, use code such as the following to determine if an instance of Excel is open:
Dim xlApp As Excel.Application Set xlApp = GetObject(, "Excel.Application")
If an instance is running you can access it using the xlApp object. If an instance is not running you will get a run-time error. The GetObject function gets the first instance of Excel that had been loaded. To get to others, you can close that one and then try GetObject again to get the next one, etc.
If you want to set the xlApp to a particular instance of Excel, you can do so if you know the name of an open workbook in that instance:
Dim xlApp As Excel.Application Set xlApp = GetObject("ExampleBook.xlsx").Application
Note:
ExcelTips is your source for cost-effective Microsoft Excel training. This tip (9452) applies to Microsoft Excel 2007, 2010, and 2013. You can find a version of this tip for the older menu interface of Excel here: Finding Other Instances of Excel in a Macro.
Program Successfully in Excel! John Walkenbach's name is synonymous with excellence in deciphering complex technical topics. With this comprehensive guide, "Mr. Spreadsheet" shows how to maximize your Excel experience using professional spreadsheet application development tips from his own personal bookshelf. Check out Excel 2013 Power Programming with VBA today!
If you manually recalculate your workbooks, you are probably doing so because of the time it takes to do the ...
Discover MoreWhen using a macro to process information in a worksheet, you may want that macro to figure out how many columns are ...
Discover MoreThe VBA programming language provided with Excel allows you to create and modify text files quite easily. Here's how to ...
Discover MoreFREE SERVICE: Get tips like this every week in ExcelTips, a free productivity newsletter. Enter your address and click "Subscribe."
2020-09-30 14:38:25
Gadi Bizinyan
You are missing an underscore at the end of the 2nd line in this part:
Public Declare Function FindWindowEx Lib "user32" Alias _
"FindWindowExA" (ByVal hWnd1 As Long, ByVal
hWnd2 As Long, ByVal lpsz1 As String, ByVal lpsz2 As String) As Long
2018-10-03 03:05:07
ashleedawg
This is NOT counting/listing Excel instances. This is counting the number of Excel *windows* - and in 2016+ each workbook is a new window but not necessarily a new instance.
This may have appeared to be correct in 2014, since workbooks opened in the same window, but still, it was only listing windows, not instances.
Also note the link to the original is broken.
2018-08-06 14:52:26
willy Vanhaelen
Disregard my previous comment. Further testing showed that the UDF doesn't provide reliable results and can not be used as an alternative for the one of this tip.
2018-08-04 09:15:41
Willy Vanhaelen
Here is a one-liner that does the job of this tip's big UDF just as well:
Function ExcelInstances() As Long
ExcelInstances = GetObject(, "Excel.application").Workbooks.Count
End Function
2018-08-04 00:14:36
Dave
Richard, the reason for the error messages is due to the fact that the workbook "FullName" required for workbooks that have previously been saved.
Eg:
Dim xlApp As Excel.Application
Set xlApp = GetObject("C:\Users\username\Desktop\ExampleBook.xlsx").Application
2018-03-21 04:24:57
Hans Hallebeek
Is there an explanation for this:
When I run the ExcelInstances function it returns 4
Does this mean that the count includes the loaded Add-Ins as instances and the Personal.xlsb each as a separate instance?
I run a xlam file that I use as interface to run several project specific workbooks.
I I do not open any workbooks and have the vba editor open and execute the function I get a count of 4
So if I really want to know what other instances besides these, I should then first make a count of loaded AddIns and the personacl xlsb and substratct these as well as the xlam I opened.
Is this assumption correct?
Thank you in advance for your thoughts.
Regards,
Hans
2017-02-13 00:17:55
matheson
PS - a decade ago, I used to use SQL queries to join the appropriate SAP tables, and extract... but they took that feature away
I fully admit that I am little more than "dangerous" on computers - but viewed the SQL complete with my Excel VBA used to allow us to put together solid algorithms for SAP guru's to eventually develop interfaces.. once we knew what we wanted we sent them our code to our Gurus to build (practical uses for the end-users).
SAP's use of Scripting appears to be foolish - I have about 10 levels of "fault handling routines" to handle all the "unexpected pop-ups" and "SAP generated messages"- and I suspect that MY Excel VBA is affecting their code (lol) - is it possible that they are the ones shutting me down?
(even all the tricks on this page no longer work)
2017-02-12 23:59:42
Matheson
I utilize EXCEL VBA scripting to :
.Open SAPGUI
.Logon SAP 740
.Assure that I am on SAP EASY ACCESS
.Start Transaction IW49N
.Populate the fields (Plant, Planning Group, Start Dates/EndDates, Layout etc)
.Initate the query.
Once the data is retrieved, it asks that the Results to be exported to EXCEL as a Table, and SAP responds by opening a Excel File (“Worksheet in Basis (1)”) in a SEPARATE INSTANCE of Excel (ie differ than the instance I am utilizing with VBA).
Originally, even though it was a separate instance – I could still “sense” the file via the Excel VBA Project List.
Hence I could change to the SAP Generated file, Select All cells, copy it over to MY Excel Workbook, then return to SAP (scripting) to close out the SAP generated Instance (“Worksheet in Basis (1)”)
That worked for a few months…. Then suddenly I was no longer to see the SAP generated file (“Worksheet in Basis (1)”) in the Excel my Excel VBA Project List…
So I started using Window API Codes, to find the File and the window Handle. This allowed me to use Window API codes to Activate the window as Excel and hence, Copy the content of the spreadsheet….
Now that stopped working…
So … anyone know the Proper way of Extracting the contents off the SAP Generated Worksheet?
2017-01-18 12:05:17
Richard
When i run getobject to grab a specific excel instance:
Dim xlApp As Excel.Application
Set xlApp = GetObject("ExampleBook.xlsx").Application
I get the following error:
Automation error
Invalid syntax
Any inputs are appreciated!
2015-08-12 20:09:24
Andrew Park
Hello,
A fellow developer obviously saw this post and used it to ensure that only 1 instance of Excel is running when the macro executes. However, we recently upgraded to Office 2013 and for some strange reason this code returns the value of 8 when executed and only 1 instance of Excel is running.
Even more strangely, when the same VBA code is executed again, the function returns 9. and keeps incrementing by 1 every time!!!
This code return a nice "1" when there was only 1 instance running in Excel 2010.
Are you sure this works in Excel 2013???
2014-12-16 03:39:26
Rob
Hi Allen,
Here's a situation I am facing. I have two instances of similar Excel workbooks. Similarity, in terms of functionalities, tabs, sheets, back-end VBA etc. Now, I'm projecting both of these instances on two different screens. I want to replicate all the actions/events/selections on one Excel instance (which I will be controlling), on the other instance as well, automatically. Is this possible? I felt this thread speaks about something similar.
Thanks in advance,
Got a version of Excel that uses the ribbon interface (Excel 2007 or later)? This site is for you! If you use an earlier version of Excel, visit our ExcelTips site focusing on the menu interface.
FREE SERVICE: Get tips like this every week in ExcelTips, a free productivity newsletter. Enter your address and click "Subscribe."
Copyright © 2024 Sharon Parq Associates, Inc.
Comments