>>A thought that comes to mind now is that the reaction to SET DELETED is inconsistent with the reaction to SET FILTER. No matter what filter is active, the SQL-query will ignore the filter anyway.
>
>There is a difference, however. SET DELETED is a global setting (for the entire current datasession, that is), whereas SET FILTER is only for a single table.
>
>When SELECTing from a filtered table, internally, the table is USEd AGAIN. When SELECTing with SET DELETED ON, this global setting also applies to the new instance of the table.
>
>Hilmar.

So, I guess this one needs revision also:

	select ;
		a.*, ;
		Iif( Eof( 'b' ), 100, b.AGpercent ) as AGpercent, ;
		Iif( Eof( 'c' ), 100, c.percent )   as PTpercent ;
		from c_srf_details a ;
		left outer join c_AG b on a.empno = b.empno ;
		left outer join c_PT c on a.empno = c.empno ;
		into cursor c_ovw1

Hmm, wonder why it has always given correct results. Or didn't it???