>There is some thought that forms that will not be sub-classed should use prgs instead of methods. The arguments are
>
>1. It is much eaiser to modify a prg. You can see all functions and procedures, therefore its easier to modify the code.

You can see them in Class Browser too. Also, doing OO-design it does not give much help to see everything (set of code tidbits) at once.

>2. You can make modifications while the form is running.

Anyway, you will have to stop to test modifications :)

>3. In general its easier to add variables and procedures to a prg than it is to add properties and methods to a form.

Again, OO-way is that no variables should be used, properties only, and you will fight object references much more often using PRGs (no this/thisform).

>4. If the client has a VFP on their site, and the prgs are excluded, you can easily step through the code as long as the prgs have been excluded in an Exe. You could even make modifications while the Exe is running on the client site.

If you want step through code, then you use Debug/Trace. I don't think that it's important to know what client runs, while you do development on separate workstation.