It appears that you want a conditional value list where selecting a value in one field controls what list of values appears in the value list for another field.
The typical approach is to define a relationship to use with your conditional value list to get the necessary filtering action.
Division::__pk_DivID = Teams::_fk_DivID
You can then set up a value list of teams listing values from Teams for fields 1 and 2, while selecting the "include only related values starting from "division" option.
This produces a conditional value list of teams if it is used from a layout based on Division.
For a working example of such a value list, check out the "basic conditional value list" example in:
Thank you philmodjunk that is exactly what I needed.
It's very helpful to first create an ERD so you can design your database. (Design before implementation.)
FMP is a great tool, but it encourages you to just "jump in" when you should design a little first.
If you check out a tool like "SQL Editor", you'll find that not only does it help you design your database, but it will CREATE the database for you in your LIVE FMP application.
When your design changes as you noted above, you have a real tool to help you maintain your DB. The "Relationships Graph" is not an ERD.
HOPE THIS HELPS.