Workload disassembling design scheme problem.

[Dawn Wu]

Dear all,
I have a hot potato to consult you all.
I have to do some monthly Charts. First, I will downloading the data of
this period and transform it into access format as a Table. To avoid re-write
the queries based on the table, I named the Tables as Current & Previous. The
queries quote the tables Current & Previous, for every month I only have to
re-new the tables Current & Previous. Thus it solves the queries re-write
problem.
Another data-complexity problem occurs. For example, There are many monthly
Charts and into them there are even more columns and rows needed to fill in.
Upon my estimation, I need to write at least hundreds of queries to generate
data source for charts. Then to fill in the charts also is a complex problem,
for example to fill in the charts, for every column it needs a vlookup
function. The workload is also heavy.
So , here comes my question. How can I simplify my monthly work while
fulfilling the charts.(For some reason, the way to write a demand to the IT
to generate the charts automatic is closed.)
Pls, my pals, give me some suggestion as how to reduce my workload on the
above two steps (step 1, write queries; step 2, put query-results into
excels’ charts).
Or, you can just think out of the box, breaking my rules, and put me forward
with a new design to disassemble the task but also can finish the charts?
Best regards.
Dawn Wu
Shanghai, China

 

[John W. Vinson]

On Mon, 28 Apr 2008 19:21:00 -0700, Dawn Wu <Dawn

Or, you can just think out of the box, breaking my rules, and put me forward
with a new design to disassemble the task but also can finish the charts?

Yes.

Use ONE TABLE with a date field.

Storing data - "previous" and "current", proxy values for date ranges - in
table names may seem to be saving you work but it's causing you far MORE work.

You can store all the cumulative data in one table with a date field
indicating the date of each record, and use Queries to select any desired
month's data, and base charts on those queries; or export the queries to
Excel.

 

[hym19]

On Mon, 28 Apr 2008 19:21:00 -0700, Dawn Wu <Dawn


Yes.

Use ONE TABLE with a date field.

Storing data - "previous" and "current", proxy values for date ranges - in
table names may seem to be saving you work but it's causing you far MORE work.

You can store all the cumulative data in one table with a date field
indicating the date of each record, and use Queries to select any desired
month's data, and base charts on those queries; or export the queries to
Excel.