I have a VFP application that uses code from another VFP application that is compiled into a UTILS.EXE file.

My first application includes the line:
SET PROCEDURE TO UTILS.EXE

Then, my first application can call any procedures that are contained in UTILS.EXE.

My problem is that when I compile my application, the VFP compiler complains that it can't find the procdures that inside of UTILS.EXE. I can just click on ignore, and VFP will make my application into a .exe which functions OK at runtime.

Note that the source code in the UTILS.EXE is not available to me so I can't just compile it into my applicaton.

Is there any way to tell VFP that the procedures are external and to not worry about finding the code? The compiler error messages are very annoying. I know that I can modify the code to call the procedures using macros (i.e. &runproc), but I would like to avoid macros if possible.

Thanks,