Hi James,

Thanks for the suggestion. When I saw your reply I was so sure that it was going to work because I remembered reading about #IF in the past. However, when I attempted to use #IF... as you've described below, I still get a VFP compile errors! The message is "Unable to find Unknown myfunc" which is not quite the same as "Unable to find Proc./Func..." when I used EXTERNAL...

I've put the #IF...#ENDIF into my startup program and no joy. Is there something else that I'm missing?

Mike

>somewhere in a program do this:
>

>#if .f.
>procedure nameOfYourProcedure()
>endproc 
>#endif
>

>That will fool VFP into thinking that the procedure is really there.
>
>
>>I have a VFP dll in which I set procedure to another VFP executable. When I run my app the dll can call a function that is defined in the executable and everything works.
>>
>>My issue is that when I build the project file for the dll, it complains that the function does not exist. If I ignore the message, the dll builds and, as I've mentioned, things work. How do I (if possible) prevent the project complaining about the function call? I've tried adding the EXTERNAL Command to the dll but VFP complains with "Unable to find Proc./Func...." when building the dll. I do not want to include the executable in the dll project in order to keep the size to a minimum.
>>
>>TIA,
>>Mike