>>>>I fixed the problem by moving the LEFT OUTER JOIN logic to the WHERE clause, obviously making it an INNER JOIN.
>>>>
>>>>Two problems with this approach. 1st, I'm not 100% sure that I don't need the outer join. 2nd, the WHERE clause approach is much slower.
>>>>
>>>>Dan
>>>
>>>Howsabout posting the posting the SQL? Maybe someone here can help you optimize it.
>>
>>Ok. Here it is.
>>
>>

>>
>>CREATE SQL VIEW "VWORKORDHDR_PDATERANGE" ;
>>	AS ;
>>	SELECT Workordhdr.*, ;
>>		Companymstr.ccompanycode, ;
>>		Companymstr.ccompany,  ;
>>		Companymstr.ccompdiv  ;
>>	FROM  ;
>>		wc!WorkOrdhdr, ;
>>		wc!CompanyMstr ;
>>	WHERE ;
>>		Workordhdr.drecdat >= ?pdFrom AND ;
>>                Workordhdr.drecdat <= ?pdTo AND ;
>>		Companymstr.icompanyid = Workordhdr.icompanyid
>>		
>>

>
>This is much simpler than I imagined. I have never heard of a noticeable speed degradation from moving a join to the where clause... does it make a difference if you move the join to the front of the where clause?
>
>
>I am still bothered by the fact that your TABLEUPDATEs weren't working using the JOIN clause. The backend shouldn't care how the cursor being updated from was built in the first place. The SQL that VFP uses to update the backend is generated usingthe properties of the view definition....
>
>Anyway, I wish I had something in my bag of tricks to help you, but I'm afraid I don't know what's going on.


That's ok. I appreciate your input.

Dan