What I see is the .PRG I have in my project (not the one used in the SET PROCEDURE) has no associated .FXP file. So I presumed that this one was not compiled. Therefore, VFP must have included in the EXE the .PRG/.FXP in the SET PROCEDURE.
The reason I came across this issue is that without having the .PRG in my PROJECT, at run-time, I kept getting the error related to the .H file used in the .PRG. Note that the .PRG is the same, in both folders, and has not been change in 2 years. Yet, I was getting the errors at run time saying the variable "INC_NAME" (#defined in .H file) not found. Maybe I should look at this issue again when I am less tired.
Thank you.
>In general, at runtime FoxPro disregards directory if it can find resource in the exe/app first.
>
>At build time, it'll most likely use the one included in the project but you'll have to test that yourself
>
>>
>>Say I have in my main.prg the following code:
>>
>>
>>set procedure to c:\myfolder\subfolder\mytools.prg additive
>>
>>
>>But in my project I included mytools.prg in a different directory (e.g. c:\myproject\programs)
>>
>>At Build time, which copy of the mytools.prg VFP includes in the EXE, the one in the SET PROCEDURE or the one in the Project?
>>
>>TIA.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
