Fabio,

>
>As to the Got/LostFocus issue,
>if you put a Grid on a Container and code into the Got/LostFocus of the Container, you can achieve the same effects as having Got/LostFocus in the Grid.
>
>
>This is not true.

This is very true, but perhaps not in your mindset.


>Case a)
>For Grid on Grid this is not true because
>when you put a container into a Grid cell,
>Container.GotFocus not fire ( Form.GotFocus is fired !)

In my 20+ years of developing, I have never seen a rational case for a Grid on Grid.


>Case b)
>I have found a case with Grid within Container when this is not true.
>I search on my problems archive a try to write a repro code.


>John, into VFP exists many redundant events;
>why VFPT it has this reticence to add GotFocus/Lostfocus in grid Class ?
>( grid have SetFocus, then a correct OOP must have Got/Lostfocus events )


There's not inate reticence, as you put it, but tyhe controls within a Grid can accept Focus events so...? Subcalss, dude. I see this as analogous to Change events.

>If BINDEVENT() worked with Form.ActiveControl,
>I would resolve the problem alone, but it does not work.
>
>Fabio

I think the main problem is you're trying to get the product to work the way you think it should and not the way it actually does. Probably, everything you are trying to do can be accomplished by subclassing controls within the Grid, my Container suggestion, et al. Try harder, Fabio.