Dragan,

For the time being I gave up, debugged this application from its own directory, found the problem and fixed the code. The next stage is to make my query work with acceptable speed (See optimizing query thread).

Thanks a lot for these ideas, I'll use them next time. We have a table, called system, which contains path string in Memo field. We're using relative paths...



>>>I never had this problem until I move my PRG files to their own sub-folder in the project folder. The only solution I found was to place a copy of the PRG files I needed to debug in the same folder as the compile APP being run. This further became a PITA when I modified the PRG and editied the wrong copy.
>>>
>>
>> Yes, I think, this is my problem. Anyway, now I'm trying to debug from its own directory. Your workaround seems quite complicated and would lead to other problems, as you mentioned.
>
>A simple thing to check in the watch window: fullpath(current.prg). If it shows you the wrong path, there you are. Also, check for atc(fullpath("..\bzprgs", set("path")) - if it's zero... you're either using relative paths, or it's really not there. Also, check curd() while you're there - you may have been moved by some irresponsible little bit of code somewhere. To set paths, I usually run something like this:
>
>

Proc setpath
>	set path to curd()
>	Do addpath with 'data'
>	Do addpath with 'meta'
>	Do addpath with 'frx'
>	Do addpath with 'scx'
>	nProg=prog(-1)
>	Do addpath with justpath(fullp(sys(16, nProg-1)))
>
>Proc addpath
>	Lparam cPath
>	<b>cPath=fullp(cPath)</b>
>	If dire(cPath)
>		If atc(cPath+',', set('path')+',')=0
>			cPath=set('path')+','+cPath
>			Set path to (cPath)
>		Endif
>	Endif

>
>So the path is somewhat longer, but then I don't get the same things twice, and I get their full paths, so even if some component changes the directory or something, I don't lose the paths. I begin with relative, but save them as absolute, just in case.