>>>Click on Column1, click the form's title bar and then drag the control that
>>>you want for the column onto Column1. Repeat this until you have all the
>>>controls in place for all of your columns. Click File from the menu,
>>>select Save As Class... You now have a custom grid class subclassed from
>>>another grid.
>>>
>>>Steve Despres
>>
>>So it's about six clicks per textbox, just to remove it and replace it
>>with a different control, for every grid I make. Wasn't OOP intended to
>>group such repetitive jobs into classes, where they get solved once for
>>good?
>>
>>I can only repeat what I've said in the other reply in this thread.
>
>Very true. I've created this one grid for use everywhere so I've only had to do this once. I've never done it again so I'd say the the OOP principles have been applied. I've even subclassed this grid to customize other grids but I didn't have to go through the process of entirely remaking it.
>
>Steve

Hi!
I do not quite agree with your method; I had done this sub-classing using
another method similar that brought up by Erik Moore, Message : RE:Subclass
grid members;
Mayby u can try that too.