I also get NONE on second table until I also added an INDEX ON DELETED().
>>Is c:\wistemp\btc_0IU0ZA4P5 a temp cursor or a real DBF? When you created the index did you create a structural index [CDX] or an IDX?
>
>It's a table and has CDX index
>
>>>Hi everybody,
>>>
>>>I'm running this simple test:
>>>
>>>
>>>SELECT sitemstr.* ;
>>> from o:\redp\dbc\ma\sitemstr ;
>>> inner join c:\wistemp\btc_0IU0ZA4P5 btcZipcode
>>> on sitemstr.zipcode = btcZipCode.btcCode ;
>>> INTO TABLE ..\..\work\query\qryU0ZA34J
>>>
>>>Temp table has an index on btcCode and SiteMstr has an index on ZipCode. sys(3055,11) shows, that optimization level for SiteMstr is full and for temp table is none. The query executes very long time (SiteMstr has ~3mln. records). The original query (not the test one) has 7 joins already and it takes forever. Is it here a way to optimize it?
>>>
>>>I've tried to change select ... where ZipCode in (select btcCode from ) form and it also shows none optimization for temp table, though seems to execute a little bit faster (still very slow).
Mark McCasland
Midlothian, TX USA