>>Well that's another matter. From what I've heard from the Fox team, it was never officially supported. It worked and I know the technique has been circulated to many places. Since it wasn't really designed to do that, it should not have been included in the official documentation, IMO.
>
>I agree that it shouldn't be included in the help in the first place if it isn't offically supported.
>
>>Now I agree that the change needs to be in the Readme simply because it needs to reference _Screen Example 1 and say don't do that!
>
>That is exactly my point. Sorry, I didn't make it clear from the beginning.

Sergey,

As Aleksey alluded to in an earlier message, this _SCREEN hook scenario was something that the product was never designed to support (i.e., ability to subclass method for object created outside definition of a class). The Fox object model is designed to support class definitions containing object subclassing whose objects are defined and instantiated based on the class definition itself. _SCREEN is really created outside (before) the context of any class definition that one can define.

As to the sample in our help file, this was an example that a customer sent in as a recommendation for us to improve our documentation. We often receive recommendations from customers as well as beta sites for ways to improve our documentation. Unfortunately, this sample was not closely scrutinized for it's adherence to our object model. We apologize for this oversight, however, we feel that meeting customer needs to improve stability of the product is a top priority which is why the _SCREEN hook functionality is no longer supported. We also want to encourage developers to start using the new BINDEVENT feature. Please continue sending in feedback for ways to improve the documentation for our next Europa version.

Randy Brown
Lead Program Manager
Visual FoxPro team