Yup, just add to project and then make sure the file is marked as excluded (IIRC when you add DLL or EXE, by default they end up as excluded). If that doesn't work, you could create PRG that simply consists of "stubs" (just the procedure and function headers) and add that to the project and mark as excluded. That should keep VFP happy when compiling.

>Well I was trying to avoid doing this in order to keep the dll size to as small as possible. Are you suggesting adding the exe to the dll project and exclude it (right click the exe in the project and select Exclude)?
>
>Mike
>
>
>>Did you try to add VFP executable to the DLL project?
>>
>>>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