[AccessD] Avoiding Duplicates on a Report

Nicholson, Karen cyx5 at cdc.gov
Thu May 19 09:46:05 CDT 2005


There should be one table that holds the customer number and invoice
number.  Then another table related to this table that holds the invoice
number with the product field.     Not six product fields, one product
field. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gowey Mike W
Sent: Thursday, May 19, 2005 10:35 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Avoiding Duplicates on a Report

 
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

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net]
Sent: Thursday, May 19, 2005 8:30 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Avoiding Duplicates on a Report



This makes me think your table's not normalized. Is this the case? 

Susan H. 

This don't work because the product I search for could be in any of 6
fields, Product1 thru Product6. 


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


-- 
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