Price Levels

[shannaj via AccessMonster.com]

I can understand what you are saying here, it makes since. So I guess what I
would do is just make my itemid the item number with a number behind it
reflecting which price level it is so I don't run in to a problem with the
primary key. Is that right?

That would actually be the easy way, but the problem is how your pricelist
table is structured. To do that, it would need to be:
ItemID
PriceLevelID
ItemPrice

The you could join it in a query using the ItemID from your Item table and
the PriceLevelID from the Customer table.

Would it make since to make a table of Price levels with the appropriate
levels indicated with the numbers 1-10 as the primary key, and then look them

[quoted text clipped - 11 lines]

 

[Klatuu]

In your price level table, the ItemID should not be the primary key. It
should be a foreign key to the item table. You can use an Autonumber primary
key for the price level table.
--
Dave Hargis, Microsoft Access MVP

I can understand what you are saying here, it makes since. So I guess what I
would do is just make my itemid the item number with a number behind it
reflecting which price level it is so I don't run in to a problem with the
primary key. Is that right?

That would actually be the easy way, but the problem is how your pricelist
table is structured. To do that, it would need to be:
ItemID
PriceLevelID
ItemPrice

The you could join it in a query using the ItemID from your Item table and
the PriceLevelID from the Customer table.

Would it make since to make a table of Price levels with the appropriate
levels indicated with the numbers 1-10 as the primary key, and then look them

[quoted text clipped - 11 lines]

up the correct price for that customer's bracket and then be able to view the
other 9 levels within the combo box. Any recommendations?

 

[shannaj via AccessMonster.com]

Perfect, this'll take me a little bit, but thank you so much!

In your price level table, the ItemID should not be the primary key. It
should be a foreign key to the item table. You can use an Autonumber primary
key for the price level table.

I can understand what you are saying here, it makes since. So I guess what I
would do is just make my itemid the item number with a number behind it

[quoted text clipped - 14 lines]

 

[shannaj via AccessMonster.com]

Okay, I have my itemlist changed. But now how do I bring all of this
together in my subform? I have the link between the tblCustomers [pricelevel]
tblPriceLevels[pricelevel] and tblItems[pricelevel]. Do I bring all of this
into a query before I do my itemdetail query? Or do I just bring it in to my
subform somehow? The pricelist I have used before was difficult enough, now
I need to figure out how to look it up. Any assitance you could give would
be much appreciated.

In your price level table, the ItemID should not be the primary key. It
should be a foreign key to the item table. You can use an Autonumber primary
key for the price level table.

I can understand what you are saying here, it makes since. So I guess what I
would do is just make my itemid the item number with a number behind it

[quoted text clipped - 14 lines]