>>In exe1 create a new "stub" prg called, lets say, stub_someproc. This stub program just calls:
>>
>>

>>   SET PROCEDURE TO the_procedure_file
>>   DO someproc 
>>

>>
>>Then in exe2 you call DO stub_someproc IN exe1
>>
>>Don't know if it will work but you can try it.
>
>as the stub is in exe1, it will work. But IMO
>
>

>   function Stub_Setproc && in Exe1
>   SET PROCEDURE TO the_procedure_file
>   return
>
>   *-- on startup of exe2
>   do  Stub_Setproc in Exe1
>
>  *-- afterwards, whenever you like 
>   DO someproc 
>

Right, yes, perhaps cleaner and to keep always using the same procedure name desired. Yes, "stub" the call to load the procedure file, then call the target procedure as normal - good solution.