Novice
Windows 7 32bit 
Access 2013
DB structure
Hello to you all this is my first message here.
I need to build up a database about recipes, ingredients, purchasing and selling orders and I'm a bit confused.
I have tried to think to a functional structure, but I am sure it will not work, especially relations-wise.
I hope the attached file will help understanding the structure, I'm sure for you it will very easy to spot the mistake.
Thanks to those providing any help.
Relazioni per gestione.pdf
VIP
Windows Vista Access 2010 32bit
I dont see a need to relate EMPS to RECIPIES.
You only need to relate tables they have a PARENT / CHILD relationship. Like 1 EMP has many PHONES.
But NOT to the recipie table. It is not a critical parent/child. Now YES, a recipie has a crated by and it is an employee but it is not needed in the relations.
Novice
Windows 7 32bit Access 2013
I did that because I need a "creator" (an employee) for every recipe, and that's a one-to-many relation because each emp can create many recipes, but each recipe can be created only by one employee.Originally Posted by ranman256
My doubts are especially on the "recipes-products" area, I don't know if this is logically working, that's all.
Moderator
Windows XP Access 2003
Relationships among/between tables are the representation of your business rules in your database structure. Do you have a description of your business and the major processes?
Here's an overview of business rules.
Novice
Windows 7 32bit Access 2013
Sure I do. Basically is what shown in the attached file on the first post.
many Ingredients + 1 Employee --> many Recipes.
Many ingredients + 1 Supplier --> many Purchasing orders.
Many Recipes + 1 Client --> many Vending orders.
You buy Ingredients from a Supplier via a Purchasing order.
You sell Recipes (Products) to a Client via a Vending order.
Each Recipe is made by one or (typically) many Ingredients.
Employees, Suppliers, Clients and References each with their details in the tables.
Posting Permissions
Reply With Quote