>I used it quite effectively for all of our forms (excuse me, screens) in 2.6 to have specific behaviors for certain functions. I even had a form of inheritance that if the screen didn't create a particular function, there was the "base behavior" in a main SET PROCEDURE file that dealt with the "default".

Sure enough. I did pretty much the same thing in 2.6.

Except, I used "messages" (and still do in VFP); makes it easier to implement new behaviour without creating a lot of new virtual or non-virtual methods (or PROCs, as in the case of FPW).