Check my other post on subclassing. Subclass grid_ in proctrls to be what you want, and that should solve the grid_toolbar issue.

On sortable columns: there is no reason not to do this, but of course I can't predict if your sorting routine will do what you want it to do in this context.

Hank

>Hank,
>
>Good point. I merged today my class and vpmctrls.vcx class, which I guess was an error. On the other hand, if I would merge my class with grid_ in proctrls, then grid_toolbar would not inherit it, since it's a subclass of devctrls.vcx grid_
>
>Or should I have merged grid_ in proctrls with my class and then redefine grid_toolbar to be based on grid_ from proctrls? What about grid_list - do we need it here or it's already built-in (I think it's built-in)?
>
>I can probably revert my today's changes and try to change proctrls
>
>Unfortunately, I faced the problem today - the working form (which is really very delicate form - one minor change and it starts breaking apart - it uses buffering 3 and set filters based on public variables in Activate) broke down - looks like I can not use my grid class with it or will have to disable sorting.
>
>BTW, what do you think about incorporating native sorting abilities in base framework grid? It sounds like a common requirement - the only problem that existing apps can break - I guess by default the sorting should be disabled then.
>
>>If you wanted to replace grid_ with what you want throughout the project, you would modify grid_ in proctrls.
>>
>>If you wanted to replace grid_ in all your projects (with certain assumptions) you would modify grid_ in devctrls.
>>
>>If you wanted to introduce an alternate to grid_ in your project, subclass grid_ in proctrls.
>>
>>If you wanted to introduce an alternate to grid_ in all your projects, subclass grid_ in devctrls.
>>
>>The problem with making changes in VPMCtrls, is that when ProMatrix introduces an update, VPMCtrls will be overwritten.
>>
>>In the case of subclassing, follow the directions in the helpfile for getting proctrls to also hold the empty subclass of the devctrls version.
>>
>>Hank
>>
>>
>>
>>>Hi everybody,
>>>
>>>I see that the grid class hierarchy is the following in VPM:
>>>

>>>Base grid
>>>           grid_  in VPMCtrls.vcx
>>>               grid_toolbar in VPMCtrls.vcx
>>>                    
>>>
>>>                  both same classes in DevCtrls.vcx
>>>
>>>                            both same classes in ProCtrls.vcx
>>>

>>>
>>>If I would want to introduce a new class here, how should I fit it into this picture?
>>>
>>>Introducing top level grdSorting in VPMCtrls would lead to too many subclasses hierarchy. Otherwise, how can I merge my functionality into existing class - hacking?
>>>
>>>Thanks again.
>>>-----------------------
>>>UPDATE. I hacked the grid and combined them both in VPMCtrls grid_ class. Going to test in a moment.