Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 29 May 2007 19:42:33 -0500
"Tony Toews [MVP]" <ttoews@xxxxxxxxxxxxxxx> wrote in
news:up2p53p5kd7dlnuckscti79klvaula90ki@xxxxxxx:
"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.
Yes, but there are different ways to store the data:
1. double the fields in a single record.
2. have two records in a single table, with identical structure.
3. have two separate tables with identical structure.
4. have a main table and then a narrow side table that records only
the discrepancies, one field per record.
The worst of all seems to me to be the 1st choice, which is, I
believe, what the OP is considering.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Follow-Ups:
- 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
- Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- From: Tony Toews [MVP]
- Microsoft Access, Double Data Entry and breaking the Normalization rule
- Prev by Date: Re: Microsoft Access, Double Data Entry and breaking the Normalization rule
- Next by Date: How can I make money with Beta
- 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):
Relevant Pages
|