>>> The problem is with the menu being the startup program for ExeA.
>
>>> The problem is that the procedures defined in your menu are not visible while
>>> ExeB is running.
>
>Jim,
>I am curious about one thing.
>Why are the procedures invisible to exeB as a stand alone but the procedures are visible to exeB when executed in the development environment? In other words, what is in the development environment that makes the menu procedures visible to exeB.

David,

The source code file for the menu. The menu generates code like this for those procedure calls;

ON SELECTION BAR 1 OF MyPopup DO Proc1 IN Menu.mpr

In the Dev env, Menu.mpr is there and VFP can load it and call the proc. In your exe env, there is no menu.mpr and ExeB can't see the program in ExeA (it can access any programs that are loaded and running in ExeA) so it tells you it can't find the proc.