S
sharp via AccessMonster.com
I have designed an Access system for keeping track of Excel spreadsheets.
The system has a GUI that allows certain critera to be entered, then creates "empty" spreadsheets from an Excel template (.xlt) These spreadsheets are populated with data by humans and saved to a central network share.
On a nightly basis, a Windows scheduled task calls a Macro in the database which opens all of the Excel sheets, extracts (Pulls) summary data from them and stores it in a table. This, obviously, takes longer and longer as more spreadsheets are added to the project.
The database GUI is also used for generating reports.
This all works fine; but sometimes, the data needs to be more "current".
So, to my question:
Is is possible / sensible to try to "Push" the data into Access from Excel (for example by using the Worksheet BeforeSave Event) using ADO or DAO? As my knowledge of Office automation is self taught, I'm probably missing an obvious (perhaps better) way to do this.
The system has a GUI that allows certain critera to be entered, then creates "empty" spreadsheets from an Excel template (.xlt) These spreadsheets are populated with data by humans and saved to a central network share.
On a nightly basis, a Windows scheduled task calls a Macro in the database which opens all of the Excel sheets, extracts (Pulls) summary data from them and stores it in a table. This, obviously, takes longer and longer as more spreadsheets are added to the project.
The database GUI is also used for generating reports.
This all works fine; but sometimes, the data needs to be more "current".
So, to my question:
Is is possible / sensible to try to "Push" the data into Access from Excel (for example by using the Worksheet BeforeSave Event) using ADO or DAO? As my knowledge of Office automation is self taught, I'm probably missing an obvious (perhaps better) way to do this.