Run time error 7867: database already open

[The_Kurgan]

Good day!
I'm running an automation process by which I open Access via Excel, run a macro, then return the data to Excel. This works fine on my computer, but my coworker gets this error when running it on his: "You already have the database open." The db is not open, however. I don't believe this to be a reference issue, as we are both using the same Excel workbook... references will be the same for both of us.

Thoughts/suggestions would be welcome. Thank you in advance!

 

[Norie]

You could run that code, with some minor additions/alterations, from Excel.

 

[The_Kurgan]

Well... maybe YOU could...

 

[The_Kurgan]

Is there a way to bump this thread so it doesn't die here? There has to be a reason it works for me and not for him... a missing DLL or something???

 

[xenou]

You could try making the DB visible first, just to see what you can see ...

'run macros
For iter = 1 To bottom_row - 1
If IsEmpty(MyMacro(iter)) = False Then
   Set AccessApp = CreateObject("Access.Application")
   With AccessApp
      .Visible = [COLOR="#FF0000"]True[/COLOR]
      .OpenCurrentDatabase MyAccessPath(iter)
      .DoCmd.RunMacro MyMacro(iter)
      .CloseCurrentDatabase
      .Quit
   End With
   Application.StatusBar = "Running macro: " & MyMacro(iter) & "... "
End If
Next iter

It doesn't sound like the problem per se but I would as a matter of course check the value of the variable too:

'run macros
For iter = 1 To bottom_row - 1
If IsEmpty(MyMacro(iter)) = False Then
   Set AccessApp = CreateObject("Access.Application")
   With AccessApp
      .Visible = [COLOR="#FF0000"]True[/COLOR]
      [COLOR="#FF0000"]Msgbox MyAccessPath(iter)[/COLOR]
      .OpenCurrentDatabase MyAccessPath(iter)
      .DoCmd.RunMacro MyMacro(iter)
      .CloseCurrentDatabase
      .Quit
   End With
   Application.StatusBar = "Running macro: " & MyMacro(iter) & "... "
End If
Next iter

PS, there's no need to bump threads in the Access forum - there's not enough activity (for now, at any rate), so all the regulars will definitely see your thread every day even if it's not at the top of the list.

 

[The_Kurgan]

Gotcha.
Thanks xenou. I'll see what I can see by making it visible. The variable checks-out.

 

[The_Kurgan]

Good news! It was cleared up. We did the .Visible = true to watch what was happening and noticed that an Access session was opening, but with a different database. Turns out, he had checked a selection in "Client Settings" to make the last used database open upon opening Access. The error message could have been better worded, so it's no wonder I was thrown-off.

Thanks for all the input!

 

[xenou]

Thanks for letting us know. That's one I hadn't heard of before ... glad you figured it out.
ξ

 

[BrianMH]

Now next time something happens like this we may have an answer