>>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.
>>
>>2. You can make modifications while the form is running.
>>
>>3. In general its easier to add variables and procedures to a prg than it is to add properties and methods to a form.
>>
>>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.
>>
>>Any thoughts?
>
>Dan,
>
>And the other side;
>
>1) The forms are no longer encapsulated and self sufficient
>2) You have to pass object references around in order to address the objects inside the form and this can cause problems if those references are not cleaned up well.
>3) You lose most of the benefits of object orientation
>4) You have a truck load of prgs, or one big one with a truck load of procs in it.
>5) You cannot see the code in the form designer or class designer
>6) The class browser cannot show you the code
>
>there are tohers but that should do.

I'm on your side. It's an office debate. Give me all of them. :)