I am designing a rules database and need some pointers in getting started. If I have several different field names from different UI's should I group all of the fields into one table? For example: tblFieldNames would contain all the possible fields names of every UI or should I break the fields names into different tables by the system they represent? I have maybe 15 different systems (UI) and all require a name field. I am thinking I should have only one table regardless of how big the list of field names may become. If I have one table for field names, how would I tie the field name back to the correct system (UI)? I can't note next to the one field name every system that uses that field that would cause dups in my table. If anyone has any ideas regarding my problem or a sample rules database schema that would be helpful.

---

Reply from Alex Hedley:

You could create a Junction Table
So the System Table
The UI Table
Then the SystemXUI Junction Table which you can create a Form to link them together.