Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 56
Default 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?
  #2   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 968
Default 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?



  #3   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 56
Default 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.
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Running Access VBA from Excel Chergh Excel Programming 1 May 21st 07 10:37 AM
How many excel processes can you open? Stanley Excel Programming 3 July 17th 06 12:19 PM
Access/Excel Communication andysgirl8800[_7_] Excel Programming 1 May 26th 06 06:36 PM
Getting Access Error Messages when running Access through Excel Dkline[_2_] Excel Programming 0 October 12th 04 09:35 PM
Multiple Excel Processes MDW Excel Programming 2 September 7th 04 05:53 PM


All times are GMT +1. The time now is 02:16 AM.

Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 ExcelBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Excel"