Long split table

[Uncle Gizmo]

The next modification you could make would be to hide the tabs along the top, one of the settings enables you to hide them, you could then use your command button to open the next Tab as suggested by Galaxiom.

I’m not 100% sure this would work, however I think there is a good chance, my only concern is sometimes when things are “invisible” code may not be able to operate on them. So I think you should set up a sandbox database and test this first.

 

[vzx]

@ UncleGizmo

thank you for all your little tutorial videos. Everything seems to be working fine (in terms of linking the tables). I was actually able to cut down the number of tables to just 3.

Just one last issue

I've numbered all the pages on the tab control as 1,2,3, etc

Now when someone clicks on the button at the end of subform, I get an error in VBA code. It appears that for some reason, access is unable to set focus on the next tab on the main form. Maybe I'm doing something wrong.

I used the following code:

    Me!tabctrl.Pages(1).SetFocus

Am attaching a copy of the DB with this post.

 

[Galaxiom]

You have the next button in a subform on the tab.

The reference to tabctrl should be via the Parent form:
Me.Parent.Form.tabctrl.Pages(x).SetFocus

A variation is to have the Next button located on the main form below the tab control. Code is used to detect the current page with the On Change Event of the tab control and then increment the index for the command to move to the next. Saves a lot of code compared to one button on each form.

The index for the current page is the Value property of the tab control.

If you wish the Caption of the button can be changed with the On Change Event of the tab control.

I would include a Back button too. The Back button should be disabled for the first page and the Next button disabled for the last page.