>Hi Terry!
>
> First I must answer to your questions. VFP toolbar object can be docked in _SCREEN or in active top-level form depending on ShowWindow property value. However the top-level form must be shown and activated before you create toolbar. This is not good and may cause form flicker or just slower initialization. You also cannot dock toolbar to form which is not top level.
>
> On the other hand, I need to show marks and pictures in dropdown menus. Mscomctl.ocx does not allows this for me. I was thinking during month about this and I even decided to create my own container-based toolbar class, but...

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

> Today I found the way to drop VFP menu in ButtonDropDown event instead of Toolbar's buttonmenu. Waw! Now I can use all features of VFP 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 VFP popup memnu for the button dropdown?

> Let me know if you need additional info and code samples. I have no time to prepare and publish such class, but maybe you can update your published example.
> It is clear that ">>" button (to show menu with button that didn't fit in toolbar width) can be added to Mscomctl.ocx toolbar. It will be not compatible with Align property other than zero, but who cares? I will make it next week.

Sometimes I have place several "contained toolbar "sections" in a single container and then added VFP 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.

I finally noticed the difference between SP 6 OCX and Themed Treeviews - there is a big (though subtle) difference. It's kind of dorky to have some controls themed and others looking like the came from a computer fair bonus table item:-).