PRB: Unable to Find Proc./Func. <Name>

MORE INFORMATION

The code example below demonstrates this error. Because the main .APP file makes reference to a procedure stored in another .APP file, the Build function is unable to resolve the reference.

1. Open a new program file. Name it SUBAPP.PRG and include the following code:

         PROCEDURE MyFunc
         WAIT WINDOW 'Myfunc called.'

2. Save the program, and include it in a new project named SUBAPP.PJX. Save the project, and build an application named SUBAPP.APP.
3. Create a file named MAINAPP.PRG. Include the following code:

         EXTERN PROCEDURE MyFunc
         DO MyFunc IN SubApp.app

4. Save the program and add it to a new project named MAINAPP.PJX. Save the project and build an application named MAINAPP.APP.
   
   During the build, as FoxPro is attempting to resolve external references, an alert will appear with the following text:
   Unable to Find Proc./Func. MYFUNC
   Locate, Ignore, Ignore All, Cancel
5. In the alert box, choose Locate and choose SUBAPP.APP, which contains the procedure MyFunc. FoxPro will add the application as an excluded application to the project MainApp and complete the build. Run MAINAPP.APP, and the wait window will appear with the text "MyFunc called."
6. Rebuild MAINAPP.PJX. Note that once again the "Unable to Find Proc./Func." alert appears. Attempting to locate SUBAPP.APP again will add yet another copy of the application as an excluded application to the project. You can choose Ignore instead, and FoxPro will rebuild MAINAPP.APP without error.

You can resolve this problem in one of three ways:

• Choose Ignore when the Locate alert appears every time you rebuild your project. -or-
  
  
• Remove the reference to SUBAPP.APP from the MAINAPP project, pack the project, and add a reference to the source program, in this case SUBAPP.PRG, which contains the source code for the procedure MyFunc. -or-
  
  
• Add the following code to the end of MAINAPP.PRG:

        PROCEDURE MyFunc
  						

  This is a procedure stub that helps FoxPro resolve the external reference. Since the line of code that actually calls the procedure explicitly specifies the file in which the procedure actually resides, it is that procedure (in this case, the procedure in SUBAPP.APP) which will be called.

Notes

Both the second and the third options will eliminate the problem. However, while the second option requires the source code to be available and that it be built into the application, increasing its size, the third option requires that the entire called application that includes the single function be sent along with the calling application. If the source code to the function is not available, and you would like to avoid the alert box, use the third method.