>The ability to subclass _Screen object was intentionaly removed in VFP8SP1 because it was "inherently unstable". The BindEvents is right way to do that in VFP8.
>VFP7 and VFP8 help for '_SCREEN System Variable Properties, Methods and Events' shows how to use _Screen subclassing for screen hooks. I belive that VFP8SP1 Readme should clearly state that it was changed/removed but it doesn't.
>
>

Hi Sergey,
I'm inclined to disagree about it being in the Readme. Since it was never officially supported/designed to do that, implementing it was a developer's decision. The developer needs to know that things might not always work that way in the future.

This instance is a little different because the Fox team made a decision to officially not support it because of instability reasons. However, if the change had been unintentional due to a change someplace else, would you feel the same?

Regards.