Splitting one table into 3 related tables

[RainLover]

Just been watching Friday Night Football.

I will tell you a secret. Relationships are not required. They are however a great tool.

The main use is to enforce Referential Integrity. This prevents a user from using a Foreign Key that does not exist as a Primary Key in the Main Table. Other than that the other use is to draw a line between tables.

When this is printed, sometimes you need A3 paper you can pin it on the wall and it makes a great Map to explain what is happening with your design etc.

I always like to create the Join. It looks better. Warning. Don't forget to tick the box "Enforce Referential Integrity." Do not check Cascade Update or Cascade Delete. You can delete a lot of records by mistake if you are not careful.

Finally with Join Type always check Number ONE. If you want you can change this in the query but in the Relationships just leave that alone.

You will work all this out in the fullness of time.

Hope this has you going in the right direction. If not just ask.

 

[RainLover]

Rain's probably asleep right now, but in answer to your question, it's perfectly fine for lookup tables to be stand-alone tables.

I've not followed the thread closely enough to answer your last question completely, but it's far from uncommon for databases to make extensive use of subforms.

Thanks for the help.

It is always welcomed.