[AccessD] Excel Graphs from Access Data - Ideas, Please

Hi Tina:

The best approach I found was to use recordsets to hold the data. Recordsets
are more flexible than tables as they can be easily modified, added to and
deleted and you do not have to worry about multiple users if you are using a
centralized BE for temp table storage.

Jim  

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tina Norris
Fields
Sent: Friday, September 22, 2006 8:43 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Excel Graphs from Access Data - Ideas, Please

Hi All,

Client is an oil and gas producer.  Daily data of several kinds are 
reported from the field on a daily basis.  Client would like to be able 
to see graphs showing, for instance, daily production for well A for a 
selectable time range (the last month, this last week, this last 
quarter, whatever) - he would also like to be able to see daily 
production for two or three wells at a time on the same graph, or for 
all the wells in a given oilfield (individually or as a total). 

Once a query is devised for selecting the date range, the specific 
wells, or the complete oilfield (separately or in combination), I want 
to export the selected data to Excel and draw the appropriate graphs.  
And, I want to do all that fairly automatically. 

The client would like users to be able to tweak data in Excel for the 
graph, if need be - as in to exclude outlying data points - but, of 
course, not alter the actual data captured in the Access data table.  
So, I am thinking of using a make-table query and sending the data from 
the "made" table to Excel.  Is this a good idea?

Some of you have done some automation with Access and Excel, so I would 
appreciate knowing what the pitfalls are that I need to be careful of.  
I am thinking to build essentially template Excel files with already 
configured graphs for the choices that are going to be offered to the 
user - which well or wells, or which well-field, and for what date 
range?  Does this sound like a good idea?

With great care, I believe I can code

I really would like your creative and technical advice, here - so, all 
ideas are welcome.

Thanks,
Tina
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com