Cumulative Data!?

George Hewitt

Registered User.
Local time
Today, 12:48
Joined
Nov 11, 2013
Messages
23
Is Cumulative data bad for access?

It must be! I am doing some work experience for a company and am convinced that entering cumulative data every week for a unique activity is bad?

For example: data entry of records unique to a marketing activity

date -------no.responses
20/01/14 - 7
22/01/14 - 14
28/01/14 - 27
31/01/14 - 31

When querying the data how on earth does one extract data? I.e. the value between 22th and the 28th it
doesn't seem like a clever thing to do. i.e. a value of 13.

For any information or guidance regarding the subject i would be thankful.

George.
 
Last edited:
Unless you have a VERY good and specific reason, Cumulative data is a calculated value, in your example 7 + 7 + 13 + 4, Just about Rule #1 of any database is Do not store calculated values.
 
Unless you have a VERY good and specific reason, Cumulative data is a calculated value, in your example 7 + 7 + 13 + 4, Just about Rule #1 of any database is Do not store calculated values.

Cheers for the information.
 

Users who are viewing this thread

Back
Top Bottom