departure dates are set in advance. a trip leaving in august may have a different price than a trip leaving in sept that was otherwise identical. There is no discount rate that can be applied across all tours. each tour will have differing pricing depending on if customers are traveling single, double, or triple. so for normalization i put the following fields into my original table:
ProductTable
- ProductID (primary key, auto number)
- TourName (text)
- Days (number)
- DepartureDate (date/time)
- SglPrice (currency)
- DblPrice (currency)
- TrplPrice (currency)
the departure date and the price structure will more often than not be unique information, arbitrary values specific to the trip and nothing else.