Thank you very much.


>Robert,
>
>Sorry I didn't check for the possibility that it may be protected. In VMP, protected properties are used for properties that are managed internally. Behaviors have been abstracted to access these properties if needed.
>
>If you need a new behavior, in this case having the ability to return an object reference to a particular toolbar, then subclass custoolbars. Specify your subclass in the oToolbars record of ??CONFIG (application specific configuration file) and VMP will use it when instantiating the toolbar manager.
>
>Add a new method that returns an object reference to a toolbar. This is similar in nature to the GetObjReftoForm method of the cusforms (form manager) object. An example of that would be:

>GetToolBarRef in cus??Toolbars
>local luretval
>luretval = .NULL.
>With THIS
>   for lxx = 1 to alen(.iatbrinstances,1)
>      if .iatbrinstances[lxx,3] = 'G' then && delaing with your singular Global toolbar
>         luretval = .iatbrinstances[lxx,1]
>         exit
>      endif
>   endfor
>Endwith
>return luretval

>Call the method and check the return value isnull to see if you got a valid object. If you have multiple global toolbars, then you could modify this slightly and check column 2 of the array for class name instead.
>
>HTH.
>
>>After I replied I checked and the iatbrinstances property is protected. I changed to public and all is well. I don't understand why you would make a property protected, but I know people do it. Is this a problem?
>>
>>Thanks
>>Robert