OK, let's talk concepts here. Strictly speaking, a form has one and only one record source. That source could be a table OR a query, and if it is a query then it could include a JOIN. However, anywhere on that form, you have only one binding - the form's .RecordSource property. Having at least two tab controls gives you extra viewing space on the same form BUT both tabs are part of the same form and have the same .RecordSource property - that of the form that contains the two tab controls. (Having only one tab control is kind of pointless.)
I think what you MIGHT want - and this is a guess on my part - is that you want a table for which you can see related tables to act on them separately. The way Access does this is that your form can have a SUB-FORM (which is a topic you can look up.) A sub-form can have its own separate .RecordSource different from the main form and can operate semi-independently from its parent. I used "semi" because usually the separate form is dependent on the main form in some way. Which actually sounds like what you tried to describe. Then you would have a parent/child form situation to correspond to an independent/dependent or parent/child table situation.
Before I go any further with this, do my comments appear to relate to what you wanted to do? I have not looked at your DB because of personal preferences to avoid opening someone else's databases on my system.