Compressing Data

B

Beth8963

I have a data base where I have different customers fill out the same form
and I take that data and make a master list of what is needed. The form
basically asks them which items (there are several) they want to see. Items
are listed in the first column, then i have 3 checkboxes that they can check
for different conditions on the item. I would like for each cutomer to fill
out a form and then put the results in one table. My problem is the big table
gives me duplicate records since not every item has the exact same
configuration of checkmarks. Someone will want condition 1 and 3 on item one,
and someone else will want condition 1 and 2 also on item one. I want my
master table to say item 1 condition 1,2, and 3. I thought of having one big
table for the customers to fill out, but I also want to keep them separate so
I know who wants what. Could someone help me with this? I hope it makes
sense. I'm not a real expert in Access! Thanks!
 
S

Sharkbyte

Beth:

I'm having trouble following the conditions issue. If Customer1 wants 1 and
3, but Customer2 wants 1 and 2, why wouldn't you want a separate record of
that? What happens if Customer1 wanst conditions 2 and 3 the next time they
order?

At a minimum, if you only want 1 product record, and have someplace where
you tie a product to the customer, I would think you would be looking at
creating an Options table, containing 8 records. 1, 2, 3, 1&2, 1&3, 2&3,
1&2&3, and None. And then associate ProductID, OptionsID, and CustomerID to
get the information you are looking for.

For conditions, does each product have a different set of conditions, or are
they all the same? Example: Product1 has conditions 1 - Blue, 2 - Red, 3 -
Green but Product2 has conditions 1 - Small, 2 - Medium, 3 - Large.

Is this an ordering system? Because the structure you described, doesn't
appear to work long-term, for ordering.

Sharkbyte
 
Top