[AccessD] Programming

Rocky Smolin - Beach Access Software bchacc at san.rr.com
Fri May 13 08:42:29 CDT 2005


Richard:

I'd only store them when response time is unacceptably slow and storing them 
solves the problem.

Rocky

----- Original Message ----- 
From: "Griffiths, Richard" <R.Griffiths at bury.gov.uk>
To: "AccessD" <accessd at databaseadvisors.com>
Sent: Friday, May 13, 2005 12:49 AM
Subject: [AccessD] Programming


Hi Group

A general programming question.  Would you ever store calculated values
in a table.  My example is this...

I have a Timesheetline table recording jobstart, jobend times/dates etc.
Do I store jobtotalhours in the table and do I store
Client charge and EmployeePaid amounts.  I would not normally store
calculated values in a table but as these calculations are quite complex
(different charge rates, time periods e.g std and overtime etc)
I thought that once calculated (at the point of data entry) why not
store these values in table (may improved report speed/programming).
Alternativley, isn't this what computers are for ie carrying out complex
calculations so why store value, when it comes to reporting on or
displaying etc simply recaculate.   My leaning now is not to store these
values. Any thoughts?

Richard

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




More information about the AccessD mailing list