Hi Richard - thanks for the great instruction! I am struggling to figure out which things go in their own table versus being fields in one giant table. Is there somewhere in your lessons that goes into that? I know its kind of subjective, but am hoping there is some magical formula that will help! thanks - Molly

---

Reply from Alex Hedley:

The Beginner Lessons will explain this.

It all depends what database you are making but since Rich uses Company example a lot we could use that.
You have a Company and Employees.
You would have a Company Table which stores information about that.
You would have an Employee Table which stores information about them.
You can create a relationship to join them.
This would be better than storing them all in one Table and having to repeat the same company name for each employee.
It also makes it easier to update the company name in one place if it were to change instead of for every employee record.