What about creating a class instead of a procedure file for each form? Not only you won't have name collision, but you could reduce redondance in the code by coding the standard behaviour in the base class and subclassing this base class for each form.

HTH

---

>I am building now an application which has a lot of controls and VALIDATIONS on each form. As this became difficult to manage all forms with the same philosophy, i've decided to create a PRG for each form, where i do SET PROCEDURE TO... (ecah program has the routines needed for THAT form).
>Everything is OK. I open one form, automatically open the PRG, and uses the procedures. When i release the form, automatically close the procedure file.
>The problem i have is: when i'm on form (like invoices, for example), and the user goes to the menu and click to see the products form, i get trouble, because those PRGs have procedure's names in common (like NEW).
>Is there anyway that i can define my procedures to become active only to that form? (i have already thought on creating methods, but i think it will become confuse).
>
>Thanks, because i'm lost! :)
>I don't mind changing now, because i'm at the beginning.