Marc,
First I'd be sure I had indexes on as many fields as possible (such as the date and product fields). Then I'd test my Rushmore optimization for queries using these tables. It's easy to have an index on dtos(MyDateField) but in the query use WHERE MyDateField < date(). Because the date clause in the query is in a different format it won't be Rushmore optimized.

Second I'd try queries in different formats to see if you need to break them up. Sometimes it helps and sometimes not, and I can't tell you why - Rushmore and SQL queries are handled internally by VFP.

But most important is to reduce the number of records that need to have the Memo field searched.

Barbara

>Ok. I will split my main table of sales. I will work with a daily table,
>which contains memo field. But some of my relation tables (e.g. products)
>have many records (75000). Also, there is a lot of criteria in the where
>clause of my query (e.g. range of dates, an unlimited choice of products numbers, departments, salors and more). I mean the query can be very big.
>
>Do you think a single SELECT SQL with many relations and many criteria
>could be used? And how can I use Rushmore or Index with my SELECT SQL?
>
>Thank you!