>>It doesn't sound right. The SET PATH statement in the code wouldn't have any effect on the #INCLUDE statement because the #INCLUDE statement is processed by compiler and the SET PATH statement is only executed when code is run.
>>The file in the #INCLUDE statement either has to be on the VFP IDE search path or you've to provide full file name.
>>
>
>You can also provide relative path. I guess it worked in Dmitry's case because he run the program and thus set the Path.

Which maybe didn't work the first time, but then the next time, if the missing definitions didn't cause an error yet, the Set Path statement was run, and then during the next run he had the path set, the .prg got recompiled with the constants this time, and it ran.

As we had it in another thread lately, the best way is to add the .h files to the project and then mark them as excluded - they aren't needed for the run time, but need to be at hand when it is compiled.