Quote:
Originally Posted by DBcurly
2 or more farms can have the same sub farm "name" field. Example; You have a farm named home, I have a farm named home.
|
This doesn't mean that my farm is the same as your farm. I could have different contracts, harvest data, agreements, tickets, or products than yours does, even though my farm is named "home" as well. If you don't need to use the
same subfarm in multiple farms, I'd remove the SubFarmDetails table between the two.
Now a subfarm, as you have it laid out, can only have one harvest, contract, agreement, product, and ticket. In fact, a subfarm is basically defined by the combination of these items. I may be mistaken, but these relationships seem reversed. You would want multiple harvests, contracts, agreements, products, and tickets per subfarm. The subfarm would exist outside of these items (I hope). If I'm on the right track, then you should include the SubFarmID as a foreign key in the HarvestInfo, Contracts, Agreements, Products, and Tickets tables.
pkstormy's advice is sound, needlessly over-normalizing will make form creation more difficult.