>[From Anderson Girardi To Matt Mcdonnell]
>
>Create a startupclass (a simp toolbat to initialize) call it as: Mystartupclass
>and its name Ex. Mystartup.vcx
>did you create a property as oToolbar and pull a initial value = .NULL.
>
>in your mainprog.exe add:
>
>set classlib to mystartup
>PUBLIC goApp
>goApp = CREATEOBJECT("Mystartupclass")
>SET CLASSLIB TO BARRA1.VCX ADDITIVE
>goApp.oToolbar=createobject("Padrao")
>goapp.otoolbar.dock(0)
>
>OBS BARRA1.VCX is the toolbar what did i create, and a call it padrao.
>
>In your form, by sample, costumers add in init event:
>goapp.otoolbar.visible=.t:
>and destroy event
>goapp.otoolbar.visible=.f:
>
>Anderson Girardi Athenas Automação e Sistemas Porto Alegre-RS/Brazil
>
>
>>Return-Path:
>>Date: Mon, 5 May 97 08:29:12 -0500
>>X-Sender: nt@[205.205.57.1] (Verified)
>>To: "Anderson Girardi"
>>
>>
>>>>What is the Best way to attach a toolbar to a FORM other than using a
>>formset? I would like to make a toolbar
>>>>class and then use it with a FORM, but I do not want
>>>>to make a FORMSET and insert the toolbar as one of the FORMS in the
>>FORMSET. Is there another way?
>>>
>>>Robert,
>>>
>>>You've posted a couple of questions about sharing methods and so forth.
>>That being the case, why DON'T you want to add the toolbar to a formset?
>>(which I don't think you can do anyway.) It sounds like you may be
>>creating problems for yourself by trying to outthink VFP.
>>>
>>>If you've gat a number of forms that need to be called within a particular
>>session in your app, maybe you SHOULD use a formset.
>>>
>>>Admittedly, there's more than one way to skin a cat....
>>>
>>>Anyway, the key in VFP for acessing methods that are part of objects is to
>>define the object with a public variable or as a property of another public
>>object and the referencially refer to the object.
>>>
>>>If you do define your app this way, make sure you're familiar with
>>WITH...ENDWITH
>>>
>>>HTH
>>
>>thanks... I will do it...
>>
>>
thanks for the information...
