>>Mike, do you mean that you'd rather have a function in a .prg than in the form that called the function?
>
>It would depend on the nature and usage of the function. If it's not used anywhere else, that function naturally belongs into a method of that form. Even better, in my way of doing things, it's a function in the bizobject used in that form - and generally it's a bizSomething.prg.
>
>And how exactly did we go back to the original question of the OOP paradigm? The famous "where does the code go?".

To these tenets "Inheritance, encapsulation, abstraction, and polymorphism" I'd add - "usability."
If I can't find, I can't use it.
Grouping modules functionally makes sense to me.
I don't expect to find accounts payable functions mixed with cash receipts functions.
Putting them in the form, or the class, the folder, or the procedure file that particularizes (love that word) these functions - all performance considerations being equal - makes good sense to me