Hi David,
I second Mike's idea to use pageframes. I've been working with pageframes and nested pageframes for years with and mostly without visible tabs.
For example ~15years ago I was experimenting with eztwain for scanning integration in an app called 'collection folders'.
There is a master pageframe that has a page for file selections (to add them to a collection), general configuration options (like M$ apps for OLE integration of XLS and DOC files) and a page for displaying the various files like txt, jpg/bmp/gif/png, doc, xls, pdf a.s.o.
Now, this 'display/viewer' page holds another pageframe with pages for displaying individual filetypes, depending on availability of M$ office apps, web browsers, pic viewers.
The activation of the master pages happens by clicking on a button in the forms ribbon
The activation of the subpages depend on the selected file(filetype) within a collection that also activate the master page if it issn't active.
The file collection is outside the master pageframe. It is positioned on the forms left side.
The masterpage that holds the sub-pageframe has two areas. The left part shows fileinfos like create date, bytes, assign date, inputfield for a filename change, date of last edit.
So, what am I using for switching the pages:
1. ribbon page changes that switch to different master pages
2. buttons in the form ribbon for switching master pages
3. listbox selection to switch pages in the sub pageframe and the master pageframe
Our customers are working with this for 15 years now and noone ever had problems with using the app and without programming knowledge noone will assume pageframes in this app. Its simply a fluent integration of something that is designed for such a kind of programming and visual interface.
If you use this approach, it won't last long and you will love the concept of working this way
JM2C
-Tom