You can make the PRG into a class and bind its methods to the form/controls events or call them directly.

>Well, you see, a lot of the functions have the same name. They just live in different prgs.
>
>This stems from another topic of debate: I delegate a lot of form-centric processing to a PRG file. User clicks "Apply" button. The click() routine does:

>do cmdApply in ThisformsPrgFile with Thisform,andOtherParms...

>
>What I need is a way to invoke a function in such a PRG file.
>
>I know there has been some debate about doing things this way. I personally have found it _much_ faster to develop apps when I package form-centric code into a PRG (one PRG for each different SCX file) rather than having to continually/repeatedly manipulate code in the form's events/methods. You can leave the PRG open for editing, tweak it, and not even have to close the form (much less modify it) in order to test your code changes.
>
>So that's what's behind my original post.