>>Jeff,
>
>>1) Make a dummy program called dbf2rtf.prg with something simple in it such as:
>>RETURN .F.
>
>>2) Compile your project and let the compiler add the dummy compiled code to >the project. Since the dbf2rtf function now exists, the error message will no >longer appear.
>
>>3) Then run MODIFY PROJECT and drill your way down to the dbf2rtf code module. >Then right click and choose the EXCLUDE option.
>
>>4) Then re-compile your project again, and this time your .exe will not have >any errors, however, the dummy dbf2rtf function is excluded from the .exe >program. At run time, your program will search for a dbf2rtf function and will >find it in the utils.exe program since you have the "SET PROCEDURE TO >utils.exe" command.
>
>>David,
>
>
>Thanks
>Jeff

---

You can do this another way too, by creating a dummy.prg. which is bound to the project, but excluded.
in that dummy.prg you can place something like:

Function Test1
Function Test2

In that case you can have multiple external functions in one prg.
You only have to compile your project once, even with David's method.
You do not need to set procedure to tthe file or something like that. The compiler does not check that. It only looks if the function is aviable somewhere in the project.

PS. I don't say that David's method is wrong. It is also a good one, but if you have calls to multiple external functions it can be handier to use a dummy.prg