Hi Cindy,

Personally, I try to avoid procedure files and put code in the containers of the controls. For example, a Save button calls a Save method in the Form. I guess I don't have a problem with PRGs philosophically, it's just not the way I do it. If I have some big, specialized crunch routine I put it into a session or custom class method and I try to group like functions into these objects.


>Do you have a guideline for deciding whether to put a bunch of number-crunching code in a form class's method or in a procedure library prg?
>
>I'm thinking that even a page or two of code that is only used with that form should be in the form class's method, but I'm used to seeing just one or two lines in the examples.