I am building a maintenance database with the help of these videos. In the lesson expert level 2 it shows how not to make a database table with baby 1, baby 2, etc.  I made a table with cost 1, cost 2, etc.  My company wants a database  that keeps up with spending per machine. I have two tables. The work order table and the asset table.  I made two more tables after watching the video access level 2 realizing I was setting up the tables wrong. One table named cost and another named part. For best practice, should I have a global relationship set up or use queries to pull the correct data on forms and reports? I am new to database design and working with Access 2010.

---

Reply from Richard Rost:

George, it's impossible for me to tell you how to set up your database without understanding the meanings of your tables and their relationships to each other. I could explain it in generic terms (customers to orders, for example) but I don't know what YOUR tables mean to you.