A number of fellow Access MVPs disagreed with the UI of a multi row tab control. John Mishefske pointed out a excellent page at the Interface Hall of Shame – Tabbed Dialogs. Of course *MY* multi row tab would not look anywhere near as ugly as some of those examples. Yeah, right.
I’ve been thinking on that today and am very much inclined to agree with them. I’m seriously considering using a list box as per the example a short way down the above page.
One suggestion was to use a Treeview control. However I’m not going to distribute any kind of OCX given the version troubles that are possible. At least not for something so minor as one form.
Performance will suffer slightly though as the user switches from one subform to the next and then back and forth as the subform would be refreshed each time.
That is I’m currently only filling the subform record source when the user clicks on the tab. This really speeds up the initial form open. So the first time on a given tab it will be slow. Currently if they switch back to the tab performance will be fast as the data has already been fetched.
If I switch to a list box then performance will be slow each time the user chooses a different subform as it will be loaded each time. Unless I have a whole bunch of hidden subforms. It’ll be at least a few weeks before I add enough tabs to that form so I have lots of time to think about what option I want to choose.