>>>>>>>Hi everybody,
>>>>>>>
>>>>>>>This is very annoying. I recompiled the whole project with recompile all option checked and tested it from command window in the same directory as a project. It stoped at my set step on correctly.
>>>>>>>
>>>>>>>Now I bring this project to another directory and try to run it, and it shows Source not available. I repeated this process few times already. If I hit step out on debugger it continues to run the whole very long code :(
>>>>>>>
>>>>>>>What can I do? I need to find out one very complicated problem and I need to debug it...
>>>>>>
>>>>>>Is the source code path part of the SET PATH command?
>>>>>
>>>>>No. Do I need to include it here? All project files are included into project and path to external files is in the SET('path'). Just in case I've included those .h files in the project (they were excluded originally), but it didn't help. I also already recompiled the main project and another one, which calls the project in question. Nothing helped :(((((((((((((((
>>>>
>>>>Modify your PATH setting to include the source directory and it should work.
>>>
>>>I added FORMS and PROGS directories and it didn't help. I'll try to add Classes and Include directory just in case. I don't know, what to do. I need to investigate some problem, but I already spent on this "SOURCE NOT AVAILABLE" about an hour :((((
>>
>>All the code needs to be available. Fox tries to resolve the calls by looking first in the current directory, then searching its path setting. If the file can't be found in either, that's when you get the source is not available message.
>
>I added these paths at the end of my path and it didn't help. How long could be set path setting? Also, everything except few include files (which were already in path) is included in the project. Why should it search for these files?

I haven't found a practical limit to the path setting. From what I've seen it looks like you're using relative paths. Naturally, if you move the application to a folder where the relative paths are no long valid, VFP isn't going to be able to resolve them. Use full paths if necessary. Note: The only time I've run into this problem is when the source isn't on the current setting.