Fabio,

You prove my point. You're not suppouse to call VFP events from you code because it's not the same as they are triggered by VFP and could cause unexpected results. The KEYBOARD command should do in this case.
I agree with you that '::' operator shouldn't be included in the VFP in the first place but that how call to a parent class method was implemented in VFP3. The DODEFAUL() was introduced later in VFP5.

>Sergey,
>
>>If you have to skip levels in the class hierarchy than something is wrong with you class design, IMHO.
>
>It is not true on general, and if this were true, it would have to remove the Scope Resolution Operator from the languages to objects and to only use dodefault() or similar command.
>
>Example:
>
>Keypress event is a true effective event if you call it within a subclass
>code.
>
>Example:
>

>* within a textBox subclass
>PROCEDURE PippoPappo
>  .....
>  TextBox::Keypress(32,0) && this send a space to the TextBox
>  .....
>

>
>but this.KeyPress(32,0) not send space.
>
>For use this.KeyPress(32,0), I need to put repetitive extra code
>

>PROCEDURE KeyPress
>LPARAMETERS nKeyCode, nShiftAltCtrl
> DODEFAULT(@m.nKeyCode, @m.nShiftAltCtrl)
> NODEFAULT
>ENDPROC
>

>
>on any subclass level of my TextBox.