Hi Nick,

This issue occurs if you create a mdb that has an import macro; once
the Access import macro runs after the Excel macro, it creates another
EXCEL.EXE instance. Use the following steps to replicate the error...
Assume you have the following Excel spreadsheet + the code listed
below:

ColA ColB
CarType Make
Ford Mustang
Chevy Impala

1) Create an Access database with a table + an import macro pointing
at the spreadsheet described above
2) Save + Close the mdb
3) Use the Excel code below to open the mdb
4) Run the Access import macro
5) Close the mdb
6) Close the Excel App
7) Go to the task manager; you will notice the EXCEL.EXE is still
present even though the physical Excel App has been closed.

hope this clarifies...


NickkHK wrote:
Joel,
Not sure I see the problem with Excel.
Explain a bit more.

NickHK

wrote in message
oups.com...
So I've encountered an error that many others have come across, but
there still doesn't seem to be a clear solution. I am trying to open
MS Access via an Excel macro and import a spreadsheet. This creates an
underlying EXCEL.EXE due to a global object being stored in the memory,
but I'm unsure how to alleviate this error. Any help/ideas would be
much appreciated. The below is the Excel macro that is opening MS
Access:

Sub OpenAccess()
Dim oApp As Object
Set oApp = CreateObject("Access.Application")
oApp.Visible = True
oApp.OpenCurrentDatabase "C:\Test.mdb"
Set oApp = Nothing
End Sub