>>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...
>
>Hi Nadya,
>
>This is just a guess, but it might be a good idea to take a look at the directory paths that are stored internally in your forms and class libraries. I.e. browse the SCX and VCX files as tables and look at what's in the CLASSLOC field. My recollection is that it sometimes happens upon relocating a project (or a piece of it) that these internally stored paths are not adjusted properly by VFP even when you rebuild with a proper SET PATH setting. The remedy I've used in those cases was to manually edit the CLASSLOC fields and rebuild the project.
>
>Mike

That may be a good idea, thanks. Fortunately, I solved the discovered problem, but it took almost whole day due to two things: 1) Source not available
2) Custom Error Handler, which intercepts my attempts to find the exact Error message...

Now, while you're in, here is a question, which I'd like to hear your expert advice.

For one-time jobs we use Standard type of query. The query may look like this:

set talk on
set escape on
sys(3054,11)
OPEN DATA l:\REDP\DBC\CT\CT
SELECT tranmstr.*,sitemstr.*,;
propmstr.*,bldgmstr.*,;
MiscLndr.LName,Apn,MapNum,BlockNum,LotNum, ;
UnitNum,WardNum,ParcelID  ;
FROM TranMstr INNER JOIN SiteMstr on TranMstr.PropID=SiteMstr.PropID ;
INNER JOIN PropMstr on TranMstr.PropID=PropMstr.PropID ;
LEFT JOIN BldgMstr on TranMstr.PropID=BldgMstr.PropID ;
LEFT JOIN MiscLndr on TranMstr.TranID=MiscLndr.TranID ;
LEFT JOIN AssrMstr on TranMstr.PropID=AssrMstr.PropID ;
where  Prefcode = "P"  AND ZIPCODE='06793' ;
and InactvFl#"A" and COMPLEVL="P" and TranMstr.SellName="Y"   ;
INTO TABLE ..\..\work\query\qryU0ZA34J

Now, I need to have all these joins (BTW, we discussed, that they probably can be modified a little bit) and if the user selects long list of zipcodes (I currently set max number to be 72), I add another join, like:

SELECT tranmstr.*,sitemstr.*,;
propmstr.*,bldgmstr.*,;
MiscLndr.LName,Apn,MapNum,BlockNum,LotNum, ;
UnitNum,WardNum,ParcelID  ;
FROM TranMstr INNER JOIN SiteMstr on TranMstr.PropID=SiteMstr.PropID ;
INNER JOIN PropMstr on TranMstr.PropID=PropMstr.PropID ;
LEFT JOIN BldgMstr on TranMstr.PropID=BldgMstr.PropID ;
LEFT JOIN MiscLndr on TranMstr.TranID=MiscLndr.TranID ;
LEFT JOIN AssrMstr on TranMstr.PropID=AssrMstr.PropID ;
inner join sometemptable on ZIPCODE=sometemptable.btcCode ;
where  Prefcode = "P"   ;
and InactvFl#"A" and COMPLEVL="P" and TranMstr.SellName="Y"   ;
INTO TABLE ..\..\work\query\qryU0ZA34J

This query seems to execute too long. (I've tested the first query with one zipcode and it was almost instantanious).

What do you think? Increase max number, so it would be, say, 5 inlist commands, or use it in where condition like zipcode in (select ...) [How much subqueiries are allowed per one Query?]

Thanks in advance.