It's not really OOP, but I actually prefer to use a form's methods as nothing more than channels into routines in a PRG file. For example, if the form is called MyForm, then I'll create a prg file called MyForm_Ctrl.PRG. I'll fill it up with procedures. Within the methods/events in the form, I'll code one line: Do XXXXX in MyForm_Ctrl with thisform (and maybe some additional parameters), where XXXXX is something like cmdClose_Click, lstItems_Rightclick, etc.

This puts all of the guts of a form's logic into a PRG file. I can develop much faster because I can tweak the code while the form is running, something you can't do if you keep the code within the form's methods. Plus you can work with the source code for all the procedures in the same editing window, which facilitates maintenance for me.

I have had no problems with performance with this approach.

Some people think this is an atrocity... so call me a heretic.

>Hi,
>
>Does anybody heard about the fact that using .PRG in an application can slowdown this application during execution, and I'd better call method in my main form that those .PRG?
>
>All the answers and opinions are welcome.
>
>Thanks