Results 1 to 5 of 5
  1. #1
    frons's Avatar
    frons is offline Novice
    Windows 7 32bit Access 2013
    Join Date
    Apr 2015
    Location
    Belgium
    Posts
    17

    Angry 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

  2. #2
    ranman256's Avatar
    ranman256 is offline VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    9,549
    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.

  3. #3
    frons's Avatar
    frons is offline Novice
    Windows 7 32bit Access 2013
    Join Date
    Apr 2015
    Location
    Belgium
    Posts
    17
    Quote Originally Posted by ranman256 View Post
    I dont see a need to relate EMPS to RECIPIES
    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.

    My doubts are especially on the "recipes-products" area, I don't know if this is logically working, that's all.

  4. #4
    orange's Avatar
    orange is online now Moderator
    Windows XP Access 2003
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,849
    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.

  5. #5
    frons's Avatar
    frons is offline Novice
    Windows 7 32bit Access 2013
    Join Date
    Apr 2015
    Location
    Belgium
    Posts
    17
    Quote Originally Posted by orange View Post
    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.
    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.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. DB Structure
    By drkepyon in forum Database Design
    Replies: 6
    Last Post: 08-14-2014, 12:11 PM
  2. How to structure my db?
    By JeredG in forum Access
    Replies: 5
    Last Post: 11-14-2011, 06:22 PM
  3. Hierachy Structure
    By anandram in forum Database Design
    Replies: 11
    Last Post: 05-02-2011, 12:20 PM
  4. New Guy Structure questions
    By cgjames in forum Database Design
    Replies: 11
    Last Post: 01-19-2011, 07:16 AM
  5. SQL statment structure
    By oss_ma in forum Programming
    Replies: 1
    Last Post: 05-13-2007, 02:08 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums