Glad you got it working. ( I have to admit, in 10 years of VFP programming I've never built an APP, until this example I've never seen a reason to.)

>It turns out this problem occured only because the custom code was compiled as an EXE. Recompiling and calling it as an APP made all programs in the main EXE available to the custom.app. This meant modifying the main exe to call an APP instead of an EXE, but that's the way it should have been done in the first place. There was no reason to use an EXE instead of an APP.
>
>>Hi Joel
>>
>>I do something similar, but distribute the custom pieces as .FXPs. The FXPs call procedures/functions in the main exe w/o problems.
>>
>>Bruce
>>
>>>I feel like this is a VFP 101 issue, but I don't remember how do do this or if it is even possible. I have a main executable that has a hook to call a custom executable. The custom exe adds a menu option, which calls a prg in the main exe. For some reason, it cannot find the program. I tried SET PROC TO MAIN.EXE, but that has no effect. It seems like that (or something like it) worked before, but I'm having no luck. Is there any way around this without modifying the main exe?