Hi Terry!

>I don't understand why they're holding out on theme-ing ToolBar and Treeview (at the very least).

It seems that mscomctl.ocx is based on outdated conceptions. Sometimes it's better "to make a new child than to wash a present one". :)))
I believe that most useful controls must be incorporated to VFP as base classes. For many years there are still compatibility problems with ActiveX controls and it seems that they cannot be solved. For example, ActiveX control may got a focus when shortcut menu is still active; VFP controls cannot recieve focus when ActiveX control is active on other form, etc.
Thus it would be great if MS implements all needed controls directly in VFP and there will be no need to use external controls.

>> Today I found the way to drop Visual FoxPro menu in ButtonDropDown event instead of Toolbar's buttonmenu. Waw! Now I can use all features of Visual FoxPro menus with OCX toolbar, even multilevel or data-based menus, mover, scrolling, etc.

>I would be interested as to how you did this. Did you substitute a Visual FoxPro popup memnu for the button dropdown?

Yes. The idea is to clear ButtonMenus collections and to run VFP menu from ButtonDropDown event. It works good for me and I will upload example this week.

>Sometimes I have place several "contained toolbar "sections" in a single container and then added Visual FoxPro combos. I had to use several containers be the special seoerator for this feature does not seem to work as advertized - or I just did not figure it out.

The ">>" button must be programmed manually. See Task Pane tool source for example code.
Unfortunately I found that my tries to add this button to OCX toolbar look ugly. I will suspend this work while I have no good solution.