[AccessD] Programming

Is it really denormalization of the data base to store actual pay rate 
because you could regard the pay rate as historically unique to each record 
even though many of them will be duplicated?

I suppose you could set up a pay rate table with start and end date and rate 
so that you could calculate historical pay based on hours, date of work and 
the appropriate date ranged pay record.

Can an audit trail table ever be truly normalized and still retain it's 
purpose of an historical record of what happened?

Rocky

----- Original Message ----- 
From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Monday, May 16, 2005 1:45 AM
Subject: RE: [AccessD] Programming


> On 16 May 2005 at 8:02, Andy Lacey wrote:
>
>> Ok, but tax, for example, is itself a calculated value, so I rest my case
>> (no chance)
>>
>
> As is Ordinary Time pay (hrs * currentpayrate) and most of the others.
>
> I'm not saying that my payroll is normalised. . I've deliberately de-
> normalised it for two reasons - speed and auditability. It's just that 
> your
> example of Nett Pay is one of the few things I haven't denormalised. I do
> calculate on that on demand :-)
>
>
>
>
>
>
>
>
> -- 
> Stuart
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>