>
The class level code for a subclass? It must exist independent from any form.>
>Must it? ;-)
I don't know. The above was a question.
>
that may be weird... and somehow reminds me of VB6.>
>Actually there may be advantages to having all of a form's code in one place. A big VFP form with code scattered all over the place may match purist OO more closely but can be a pita.
Agree. I prefer to have most of the code in a prg-based bizobject (one or more), while the visual parts are pretty much codeless, keeping only the part where they care of their looks - conditionally visible, shifting focus, page jumping, one-liners like thisform.CodeToRunWhenThisButtonIsClicked() and other stuff of the kind. The logic goes to bizobj.
Though, if I have a button six levels deep in membership hierarchy, where's its .click() code? At the form level?