[AccessD] Avoiding Duplicates on a Report

Thanks everyone for the advice, I will certainly look at normalization.
But for now how do I do about concatenated??  I have not heard of this.

Thanks 

-----Original Message-----
From: Darsant Silverstring [mailto:darsant at gmail.com] 
Sent: Thursday, May 19, 2005 8:41 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Avoiding Duplicates on a Report

On 5/19/05, Gowey Mike W <Mike.W.Gowey at doc.state.or.us> wrote:
> 
> What do you mean by normalized?  The customer has the ability to 
> purchase up to 6 products on one invoice.  The table assigns the 
> invoice number and than records the products selected in the fields 
> Product1 thru Product6.  The customer# is pulled from the customer
table.
> 
> Mike Gowey  MCDST, A+, LME, NET+
> Team Leader - East Region
> Information Systems Unit
> 

In a normalized database, if the customer purcahses 6 products, there
would be a sub-table such as InvoiceDetails, where you would have the
InvoiceID and then a seperate record for each product purchased.

One of the problems with doing it as a field on the invoice is you end
up with hard limits (using a subtable, the user could in theory,
purchase as many or as few products as they want). There's many other
reasons for normalization but I think that's left for another day.

However, to the problem at hand, since the data is not normalized best
bet would be to fake it and concatenated the fields as suggested
earlier.
--
Darsant Silverstring 

"Peace cannot be kept by force. It can only be achieved by
understanding."
-Albert Einstein
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com