Very coherent. I don't know what the underlying difference is between CREATOBJECT and ADDOBJECT (Edward probably knows all these things *G*) so I don't know when one should be used over the other or CAN be used over the other.

However, that aside, i can now apreciate where you were heading in regards to Michel's problem. As I now understand it, you and I seem to be headed in the same direction with the only difference being the base object class. The toolbar would still be created in code within the base object. Right?

>No offense taken at all, Bruce. As I said, I was just musing. And, despite what the blue envelope may imply, I'm learning as I go, too :-) I also CREATEOBJECT my app object. But when other objects are created, I want to ADDOBJECT them to the app object.
>
>In my just-departed-job I retrofitted an application object over the top of a two-year old 3.0 app. There was a LOT of very nasty code in it--just learning kinds of things and inherited, too. So, I ended up defining a app class that was based on a formset. I couldn't use a different class because there are many objects that you can only add to a form/formset. So, for example, an installation could have any one of 50+- forms (modules) with customizable toolbars installed for their needs and the users had control over where and when a form was available to the interface. But I wanted to have each form be a member of the application object--when it was called.
>
>Anyhow, I kept running into trouble adding objects to non-formset application objects (of course) so I went ahead an implemented it. It's not the lightest weight object. Starting from scratch I would choose a line class as my application object base class.
>
>So, I was thinking that if Michel Creppy really wanted to see his toolbars in a form object rather than using the class designer, one solution would be to use a formset for the application object and then you could add toolbars to the formset.scx. I'm not sure I'm being at all coherent, but I am really trying! *bg*
>