I don't think you are as close to being finished as you think. Your relationship would be better off with some key changes.
You have a Budgets table that links by a name field to other tables. Linking by such name fields is very problematic. Names are not unique. Names are subject to change in the future. If you mis-enter a name in one of these fields used as relationship keys, create some related records and then discover the error, correcting the error can break the record's links by this name to other records.
The records should be linked by number fields that auto-enter a serial ID number on the "one" side of the relationship to a matching number field (without the auto-entered serial number setting) on the "many" side of the relationship.
Example: as I read your Relationships Graph, you'll likely have many budget items for a given university record. Define a UniversityID field as an auto-entered serial number and link it to a number field in budgets of the same name. When you need to refer to the University Name and other fields in the University table from a Budget record or layout, you can do so directly via this relationship. A calculation can refer to Universities::University name to refer to it's name. If you put Universities::University Name on your layout, it will display the University Name for the record related to your budget record.
When you create a new record, you set up your Budget::UniversityID field with a drop down list or pop up menu of University ID's in field 1 and University Names in Field 2. You can then select a university by name from this list and the value list will inter the required ID into the field.
If you are on the budget layout and you need to create a new university record, you'll have a problem as you'll need to create a new record in the university table before there is a UnivesityID number that you can use to link it to your current budget record. (The same problem exists when you use the University's name to define the relationship.) The solution is to switch to the University Layout, create the new record, then take the ID number of the new record and return to the Budget layout where you enter this ID number. This can be scripted:
Go To Layout [Universities]
Set Variable [$UniversityID ; Universities::UniversityID]
Go To Layout [Original Layout]
Set Field [Budget::UniversityID ; $UniversityID]
Note: this does not enter any data into the new record in Universities. With this script, you would need to either place fields on your Budget layout from the Universities table so that you can enter new data, such as the name into these fields, or you'd have to switch over to a Universities layout and update it later.
The alternative approach is just to use a button to switch to the Universities layout. After creating the new record and entering the data, you can then switch back to Budget and select the new Univerity layout from the drop down or pop up menu.