>>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.
>
>
>I do that by having one dummy.prg where I create all procs names (empty of course) from the exe I am setting procedure to.
>Dummy.prg is included in the project, but stored outside regular project structure (away from other prgs) which becomes 'visible' to EXE after compiling. Compiler does not complain as it finds procs in dummy, while at run main exe does not complain either as it finds those procs in that external exe. ( Enabled by set proc to ... additive with keyword 'additive' being very important! )
>
>I am not sure if this is _proper_ solution but it just works.
>However I did not try this when compiling into DLL. It works for one exe referencing procs/funcs in another exe.
>
>HTH
>Sergio

Hi Srdjan,

"Proper" or not, a dummy.prg did the trick. Thanks to everyone for their input.

Mike