Jeff,

Look at the EXTERNAL command in the VFP Help, that should do the trick.
In your case EXTERNAL PROCEDURE NameOfExternalProcedure should be used.

>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.

Regards,