>David,
>
>FWIW, I've never ever coded anything in a CommabdButton When or Valid method. They make no sense to use in the context of VFP and I think they are holdovers in an attempt to make 2.x code port easier. It sounds like you are porting 2.x code. I completely junked my 2.x stuff and redid my UI in VFP.
>
>If I want to prevent a user from clicking a button I'd .Enabled = .f. If I wanted to know when a button got the focus I'd use the GotFocus() event to notify me, I can't actually say that I've ever wanted to do this. What we used to put in a 2.x button Valid() belongs in Click().
>

The point of my example was to show how important it is to know how these classes behave. I'm not surprised that someone with your experience has a way of implementing my example that's more in harmony with VFP,OOP, etc. The point is, I'd like to have a chance at learning how to harmonize without running into EVERY gotcha the hard way. That's what a good interface spec is for.

>You do have complete control over VFP objects NODEFAULT and BaseClass::Method() allow you to alter the normal flow of event sequences.

Depends on what you mean by complete control. What I meant was having both the knowledge and the means...not just the means.

...so I'll get Hacker's and see where it takes me...

Thanks for responding.