Trying to find the best way to structure this . . .

I'm creating a database that tracks customer information, brand information
and item information. Customers have brands and brands have items. Most of
the information is item specific. There is a unique customer identifier (call
it a customer number for the sake of argument). Brands are also unique and
items are unique based on SKU#.
I want to be able to relate a one to many relationship from customer to
brand and customer to item as well as from brand to item.
I will be creating forms for data entry and reporting.
Ideally, the user should be able to query information on an item, brand or
customer and see the related information.
I'm kinda taking this over for someone and have decided to just use the data
collected and start over.
Any suggestions for best structure for this?

Use the query designer:

Put the three tables and relate customers to brands, brands to items. Put
the fields from the customers and items in the query grid and you will be
related correctly.

Bonnie
http://www.dataplus-svc.com

Piperlynne wrote:
I'm creating a database that tracks customer information, brand information
and item information. Customers have brands and brands have items. Most of
the information is item specific. There is a unique customer identifier (call
it a customer number for the sake of argument). Brands are also unique and
items are unique based on SKU#.
I want to be able to relate a one to many relationship from customer to
brand and customer to item as well as from brand to item.
I will be creating forms for data entry and reporting.
Ideally, the user should be able to query information on an item, brand or
customer and see the related information.
I'm kinda taking this over for someone and have decided to just use the data
collected and start over.
Any suggestions for best structure for this?

--
Message posted via http://www.accessmonster.com

TblCustomer
CustomerID
CustomerFName
CustomerLName

TblBrand
BrandID
Brand

TblCustomerBrand
CusatomerBrandID
CustomerID
BrandID

TblItem
ItemID
Item
SKUNum
BrandID

TblCustomerBrand records a Customer's Brands. TblItem records each Item and
its Brand. You don't need to directly relate Customer to Item because a
customer is related to all the items in each of the customer's brands in
TblCustomerBrand.

Steve





"Piperlynne" wrote in message
...
I'm creating a database that tracks customer information, brand
information
and item information. Customers have brands and brands have items. Most of
the information is item specific. There is a unique customer identifier
(call
it a customer number for the sake of argument). Brands are also unique and
items are unique based on SKU#.
I want to be able to relate a one to many relationship from customer to
brand and customer to item as well as from brand to item.
I will be creating forms for data entry and reporting.
Ideally, the user should be able to query information on an item, brand or
customer and see the related information.
I'm kinda taking this over for someone and have decided to just use the
data
collected and start over.
Any suggestions for best structure for this?