Data Storage

[Coach Ty]

Hello,
I'm not sure if this is a question specifcally for the tables board or for reports. But here is my question:
I run statistics that are based on many queries and I need to store the results of the queries on a weekly basis according to the date the queries are ran.
Is it best to store the results by using an append query that will ad to a table that was originally created with a make table, based on the query being ran weekly?
Or should I run weekly reports based on the queries and save those reports?
The stats ran are always the same, using the same queries. They are ran weekly for each employee and need to be stored in each employee's file by the date the stats are ran.
My purpose is to have an ongoing performance analysis, where I can track the employee's performance over time and generate a monthly analysis.
Can someone please tell what would be the best way to accomplish this?
Thanks for your help ...

 

[Galaxiom]

It is normally considered bad practice to store derived values in a table unless the original data is being deleted or there are so many records that it is impractical to recalculate on demand.

Your queries should be designed to recover information from any time period directly from the original data whenever you want it. Your monthly analysis should also work with the original data.

How important is it to actually keep the information in the employee files at all?

 

[Coach Ty]

I have the basic information being input into a table using a basic form. Everytime I input the information it's dated.
Need to store the information by date so that I can graph the performance from one date to the next, over the course of months.
When I input the information, each time into the table, it would appear that I'm simply changing the date and re-entering the same inforamation each time.
The table that I have contains all of the employees and all of the calculated statistics in a number of fields.
The information contained in the fields is used in queries to obtain the statistical information. The queries are run weekly, so I need to find a way to store the results from week to week, to track performance progress.
If I was using the system to calculate the cost of various items sold on a specific day, to a specific customer, where would this information be stored in the system, so that I could look back to see what a specific customer spent on any given day?
I just need to be able to recall a specific date to see what an employees stats were on that date.
I'm just not sure where to maintain the information results, of the queries, when I have to run the same queries each week?

 

[Galaxiom]

If you only want the summary of the data as calculated by the weekly queries and have no further use for the detailed data then it would be appropriate to append the query results to another table. This way you can create further reports based on the weekly summary data.

We would need to know more about the summaries to suggest the best way to hold them in a table.