>I'm not sure how helpful this will be, but you can usually avoid empty(), which is NOT optimizable.
Or, use empty(), precisely to avoid full rushmore optimization, since this will sometimes slow things down. Read my recent entry in FAQ. Especially an expression like "FIELD # 0" may select too many records.
Hilmar.
>
>for instance:
>
>field={}
>field=' '
>field=0
>
>Could make a big difference.
>
>I've also found that the order of the statements in the WHERE clause can make a big difference. It seems that putting those that filter the most records first is best, but you might want to play around with the order a bit. VFP's reporting of opimization is not the end-all of optimizing your SQL.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
