Running MS Access From Excel VBA: Communication Between Processes?
 

Excel spreadsheet has an "Import" button.

Clicking it creates an instance of MS Access through which we open up
a .MDB and pull some strings that causes the .MDB to munch on some
data and push it into the spreadsheet.

Minor cosmetic problem: it's a fairly long process and all the user
has to go on is an HourGlass cursor.

If it's not too big of a deal, I'd like to have the MS Access app push
progress messages back up to the Excel VBA routine - or have the Excel
VBA pull same from MS Access.

Anybody done anything like this?

Running MS Access From Excel VBA: Communication Between Processes?
 

Why not just run queries in the jet MDB using DAO or ADO from Excel VBA?
Then the Import button is in control and you can do progess messages as
required.
And of course it will be faster since you don't have to create an instance
of Access.

Charles
__________________________________________________
The Excel Calculation Site
http://www.decisionmodels.com

"PeteCresswell" wrote in message
...
Excel spreadsheet has an "Import" button.

Clicking it creates an instance of MS Access through which we open up
a .MDB and pull some strings that causes the .MDB to munch on some
data and push it into the spreadsheet.

Minor cosmetic problem: it's a fairly long process and all the user
has to go on is an HourGlass cursor.

If it's not too big of a deal, I'd like to have the MS Access app push
progress messages back up to the Excel VBA routine - or have the Excel
VBA pull same from MS Access.

Anybody done anything like this?

Running MS Access From Excel VBA: Communication BetweenProcesses?
 

On May 28, 10:14 am, "Charles Williams"
wrote:
Why not just run queries in the jet MDB using DAO or ADO from Excel VBA?
Then the Import button is in control and you can do progess messages as
required.
And of course it will be faster since you don't have to create an instance
of Access.

Charles

Sounds like the answer to "can I push/pull messages from the MS Access
app.." is no.


That being the case, now I see the light.... and next time... or if I
get some breathing space on this one... I'll decompose the .MDB
processing into many callable routines and then call them one-by-one
from the Excel VBA.