Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: "Tony Toews [MVP]" <ttoews@xxxxxxxxxxxxxxx>
- Date: Tue, 29 May 2007 20:23:27 GMT
"hippomedon@xxxxxxxxxxxxxx" <hippomedon@xxxxxxxxxxxxxx> wrote:
On the other hand, it seems that it might be easier to "de-Normalize"
the table slightly to have a [DtaRspn1] and a [DtaRspn2] field.
This is not denormalizing. You have the same data but entered twice. It's
perfectly legitimate to do this.
At the concept or overview lefel this is similar to storing the cost and price of an
item when you sell the item. After all the cost and price could change moments
after the transaction is entered.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
.
- Follow-Ups:
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: David W. Fenton
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: hippomedon@xxxxxxxxxxxxxx
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- References:
- Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: hippomedon@xxxxxxxxxxxxxx
- Microsoft Access, Double Data Entry and breaking the Normalization rule
- Prev by Date: Re: Access 2003 create text based on decimal numbers
- Next by Date: Showing a sum in a form based on a query or another table
- Previous by thread: Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- Next by thread: Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- Index(es):