VFP'll report partial optimization if there's no index on DELETED() and SET DELETED is ON. It's not new to VFP9. It doesn't mean that adding index on deleted() will speed up the query, though. See http://members.cox.net/cs-vfp/OutFoxed15.html

>>> Well, it didn't mess up the displayed data, but now SYS(3054,12) gives the following with all codepages at 1252:
>
>

>Using index tag Ejbelagg to rushmore optimize table sofe110
>Rushmore optimization level for table sofe110: partial
>Using index tag Subartnr to rushmore optimize table sofe301
>Rushmore optimization level for table sofe301: partial
>Joining table sofe301 and table sofe110 using index tag Opprgr
>

>
>
>Still not fully optimized as in VFP8, now only partial!
>
>

>Index for Sofe301.dbf:
>Tag:      Key:
>RADNR    SUBSTR(ARTNR,11,8)+STR(RADNR)
>RADTYP1  ARTNR+RADTYP
>RADTYP2  SUBSTR(ARTNR,11,5)+RADTYP
>PRGRUPP  ARTNR+PRGRUPP
>RADNR2   ARTNR+STR(RADNR)
>RADTYP   RADTYP+SUBSTR(NAMN,1,18)
>RADNR3   SUBSTR(ARTNR,11,5)+STR(RADNR)
>SUBARTNR SUBSTR(ARTNR,11,8)
>PRGRUPP2 PRGRUPP
>
>Index for Sofe110.dbf:
>Tag:      Key:
>OPNR      OPNR
>OPPRGR    PRGRUPP
>OPPRAV    PRAVSN
>EJBELAGG  EJBELAGG
>
>