Nancy,

Actually see my earlier reply. One designs forms in the form designer,
then one can do a NEW \ FORM from the designed form. You then
have a form based on MYFORM class, which has the basic functionality
for your company, and you design your form, etc.., etc...

The same applies to command buttons, text boxes, etc....., almost
everything visual. But, somehow, not toolbars because, then,
you have to have a formset.

Do you get what I am getting at ? And it is because I wanted to
subclass toolbars in the same way that I do everything else, that
I used the workaround to temporarily make my default form class the
MYTOOLBAR class.

Michel.
=============== Your original message follows =================

>Hi, Michel
>
>Edward has already answered your question, but since you've been copying me on your replies...I'll just add an "amen" to Edward's comments.
>
>You visually design toolbars in the class designer. Isn't that how you got your toolbar class you mention in the first place?
>
>If you have designed the toolbar class in the class designer, then there is no need whatsoever--at all--to jury-rig a form object based on the toolbar class. You have everything (except a DE) accessible to you from the class designer.
>
>>How do you design the toolbar then ? You are not inferring designing
>>it the long way round in code when one could do it visually, are you ?
>>
>>Give me another way to design a toolbar visually, with all the buttons that you
>>want, interactions, method code, etc..., and I'll gladly jump at it.
>
>
>hth