Hi Alan,

> Although, I have to play a bit with Craig's solution. It looks very weird on my system. No bottom border, and if I dock it, undocking it becomes a real issue, and once it does get undocked, I only get the bottom half of the toolbar at all.

Craig's stripped toolbar is a proof of concept. You have to play with the values being sent to the SetRegion() API to get a toolbar that display's only its child container. I suspect that the most accurate way to eliminate a toolbar's chrome may be a combination of sysmetric() calls and a bunch of hard coded constants for measurements such as toolbar margins. I believe that each edge of the toolbar may have a different margin?

> I'll play with it for a while though, because it surely shows some promise.

I'm excited by Craig's stripped toolbar because I think it creates the perfect container for building professional GUI's using VFP. When you strip the toolbar of its "chrome" (titlebar, border, and margin) and add a single container to the toolbar, all you are left with is the container itself. All your work takes place in this container which you can visually style and control as you wish.

Christian's contributions are the 2nd piece of the puzzle. Christian has demonstrated how the container within a toolbar can be smoothly moved via click and drag WITHOUT the container's toolbar entering a docked position. This is critical because VFP does not support a native way to prevent toolbar docking. Christian's code provides the workaround for this as well.

Many, many thanks to you Christian and Craig!!! :)

Malcolm