open xls workbook, check if already open

Posted on 2013-12-09
Medium Priority
Last Modified: 2014-01-07
In MS Access I want to first check to see if Excel is open.  If so, check to see if a certain workbook is already open.  If not open it, otherwise set the open workbook as the active workbook.

Here is what I have so far.  Almost there but if it is already open it gives a warning about re-opening an open workbook.

Private Function UpdateCrisisChart()
Dim xls As Object
Dim wrk As Object
Dim Sheet As Object
Dim strExcelFile As String
    If IsExcelRunning Then
        Set xls = GetObject(, "Excel.Application")
        Set xls = CreateObject("Excel.Application")
    End If
    xls.Visible = True
    strExcelFile = GetExcelFilename(Me.SDate, "Adult")
    Set wrk = xls.Workbooks.Open(strExcelFile)
End Function

Open in new window

Question by:KCTechNet
  • 2
  • 2
LVL 120

Assisted Solution

by:Rey Obrero (Capricorn1)
Rey Obrero (Capricorn1) earned 1000 total points
ID: 39706883
< but if it is already open it gives a warning about re-opening an open workbook.>

if you can get the error number from the warning message, grab that error code and
use it in your code to divert to the open workbook.

Author Comment

ID: 39706935
Sounds good.  So on error trap, what do I use instead of .Open in:  
          Set wrk = xls.Workbooks.Open(strExcelFile)

Author Comment

ID: 39707225
I should mention I am concerned if they have multiple workbooks open,  one of which is the one I need.  How do I set the one I want as active?
LVL 61

Accepted Solution

mbizup earned 1000 total points
ID: 39708365
You need to
1. error check to see if an existing instance of excel is open and respond accordingly
2. Check for the desired workbook and activate, create or open it accordingly

Try this, and read the inline explanations:

Sub DoStuffInExcel()

Dim xlApp As Excel.Application
Dim xlWB As Excel.Workbook
Dim xlWS As Excel.Worksheet
Dim wb As Excel.Workbook
Dim strPath As String
Dim blFound As Boolean

' This is the path/file we're working with -- change as needed
strPath = "c:\Test\TestXYZ.XLS"

On Error Resume Next
    Set xlApp = Nothing
    ' Try to use currently open application
    Set xlApp = GetObject(, "Excel.Application")
    ' If that fails, create a new application
    If Err = 429 Then
      Set xlApp = CreateObject("Excel.Application")
    End If
    On Error GoTo EH
    ' See if the workbook you need is currently open.  If so, set it as the workbook object.
    For Each wb In xlApp.Workbooks
        If wb.Name = Mid(strPath, InStrRev(strPath, "\") + 1) Then
            Set xlWB = wb
            blFound = True
            Exit For
        End If
    ' If not, then see if the file exists
    If blFound = False Then
        If Dir(strPath) = "" Then
            ' If it doesnt exist then create it
            Set xlWB = xlApp.Workbooks.Add
            xlWB.SaveAs strPath
            ' Otherwise open it
            Set xlWB = xlApp.Workbooks.Open(strPath)
        End If
    End If
    xlApp.Visible = True
    '  The rest of your code goes here
    ' Use the close and quit commands if needed.  If now, remove those lines but keep the = nothing lines.
    ' Close the workbook and clean up the objects
    Set xlWB = Nothing
    ' Quit Excel and clean up the object
    Set xlApp = Nothing
    Exit Sub
    MsgBox "Error " & Err.Number & ": " & Err.Description
End Sub

Open in new window

LVL 61

Expert Comment

ID: 39708394
As an aside, I'm using "Early Binding" in my code, declaring the excel objects like this:

Dim xlApp As Excel.Application
Dim xlWB As Excel.Workbook
Dim xlWS As Excel.Worksheet
Dim wb As Excel.Workbook

Open in new window

This makes for easy programming, because you get auto completion of your commands in the VB Editor,

However, if compatibility across multiple versions of Office is a concern, use late binding instead - declaring these as generic Objects:

Dim xlApp As Object
Dim xlWB As Object
Dim xlWS As Object
Dim wb As Object

Open in new window

The downside to Late Binding is that you lose the intellisense/autocompletion in programming, and possibly take a slight performance hit.

I typically keep both versions in my code and switch between them - commenting out the late binding in favor of early binding to get auto completion, and then switching back to late binding before deploying an application so that it will work regardless of Office version.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article shows how to get a list of available printers for display in a drop-down list, and then to use the selected printer to print an Access report or a Word document filled with Access data, using different syntax as needed for working with …
Sometimes MS breaks things just for fun... In Access 2003, only the maximum allowable SQL string length could cause problems as you built a recordset. Now, when using string data in a WHERE clause, the 'identifier' maximum is 128 characters. So, …
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…
Suggested Courses

597 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question