First, create the main form, bound to Table1.
From the Toolbox (View menu), add a tab control to the form.
Place the controls from Table1 onto the first page of the tab control.
There are many ways to make a subform, including using the subform wizard in
the Toolbox. My preference is to actually create a form, and save it. Then
open your orignal form, select the 2nd page of the tab control, and drag it
from the database window. Then right-click the edge of the new subform
control, and check its Properties. On the Data tab of the Properties box,
you should see the name of the main form's primary key as the
LinkMasterFields, and the name of the subform's foreign key as the
LinkChildFields.
Normally, you would create the 3rd one as a subform of the 2nd one. If you
want it to be in the next tab page of the main control, add a text box to
the main form that reads the value in the 2nd subform. This text box will
have a ControlSource of:
=[Sub2].Form![Text2]
where Sub2 is the name of the subform control, and Text2 is the name of the
text box for the primary key. You will then use the name of this text box as
the LinkMasterFields for your next subform. It is possible to skip the text
box and use the reference directly in LinkMasterFields: there's an example
of that in the Customer Orders form in Northwind.
You may find that it starts to become unweildy to take this approach to the
4th level. There are potential traps, such as crashes related to Conditional
Formatting, code in Form_Current, Name AutoCorrect, and performance issues
related to subdatasheets, not to mention the ineffieincy of loading and
synchronizing lots of forms like that, and most importantly the
user-overload of trying to understand an interface like that.
Would it be preferable to break the form down into separate interface parts
instead of making one monster?