>Hi Folks:
>
>I have 33 UPC codes that will have four different prices attached to each
>UPC depending on which one of four head offices is selected
Ok...
>Can anyone offer a better solution than a separate cost table for each head
>office linked back to a HEAD_OFFICE_# table?
Yes indeed. Storing data in a tablename is a VERY bad idea. What if
the company expands and you have to deal with seven offices!?
>Any assistance would be appreciated
PRODUCTS_TABLE
I'd suggest just calling it Products. You know it's a table. <g>
UPC (PK)
NAME
NAME is a reserved word in Access and may give you trouble; maybe
call this ProductName.
DESCRIPTION
SIZE
PACK
COST
Offices
OfficeNo
OfficeName <e.g. "Bristol", "Poughkeepsie"
<any other needed info about the office as an entity>
Pricing
OfficeNo ' FK: which office
UPC ' FK: which product
CaseCost
If there is a product sold out of four offices, there would be four
records in this table.
John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps