Barbara,

Thanks for the response. Ok, now I'm in small ("v men'shinstve"). I thought calling Object.Init method from another object method breaks events sequences, but I may be wrong here, since you, Nick and Cetin don't consider it's being something ubnormal...

Ok, thanks again.

>Nadya (and Nick)
>Just IMHO, but I agree with Nick about re-using the INIT() code. I started doing this when I realized that I had several subclassed grids and they all repeatedly called code that was called from the INIT(). For several I used a single subclass with a "ShellFromInit" (or in Visual Maxframe their ShellAdditionalInit() ) method but others needed more complex coding and each grid seemed to be different. I was ending up with multiply nested methods.
>
>Finally I opted for just putting the code that was always needed for resetting properties into the INIT() and only putting code called under special circumstances into a separate grid method - it was simpler, easier to track and always the same no matter whether I was using a grid from VMF, a VFP base class grid or Nick's Highlighter grid.
>
>Just my $.02 US
>Barbara
>
>>Nick,
>>
>>I don't know. Let's see, if anyone else will support this suggestion. I'm just telling you, that it's a little bit confusing, especially, if somebody doesn't know the specific. I can not remember in my code when I call object.Init() from another object some method (forget about CreateObject/NewObject for a moment). Cetin has something similar in his MultiSelect grid, but I don't like it, so I changed it to be GridInit method :) in my version of his class...
>>
>>Anyway, as I already said, it's not a big deal and we can perfectly live with it...
>>