>> About Booleans: use explicit logical field =.t. or logical field = .f. in your SQL to make it Rushmore optimizable, if you have an Index on this logical field.
>
>I meant Boolean operators, AND, OR, NOT...not T/F as in some languages.
>
>And no offense, Nadya, but that may be the worst thing to do. Putting indexes on logicals means often carrying large chunks of the index across the wire...so in a WAN or RAS especially, that may not be a good way to go. The VFP Rushmore Help is woefully lacking in this area, as the discovery of this problem is fairly recent...

Thanks for the tip, Bruce. AFAIK we don't use indexes on logical fields except for deleted().