That is a conundrum, Ria.
You say that you changed nothing else but the INDEXes in the table and now it runs slower??
I assume that none of the indexes defined have a "NOT" in them and are not UNIQUE in addition to being "simple".
I assume that the indexes all live in a .CDX file.

Can you give us some samples of the queries?
Do you have an index on DELETED() perhaps?...And if you do, do you have a reasonable number of records actually deleted in the tables with that index?
- If you do have such a TAG(s) then they can slow things down a lot IF the actual number of deleted records is low (and assuming that you run these with DELETED set ON.
Is it possible that you ar running on a machine with low RAM? I would guess that when the indexes were NOT Rushmore compliant, then they weren't used and so didn't occupy RAM too much, whereas now that the comply they will want lots of RAM.

These are some ideas. Good luck.


>Hello!
>I have a FoxPro application, that handles large volume of data. The tables have simple indexes defined on its fields. In an attempt to speed up my queries, I modified my indexes to match my queries. I read about Rushmore optimization and altered the indexes so that they obey the Rushmore principles.
> - My indexes look exactly like the query.i.e if my query defines a criteria as 'Alltrim(Upper(fieldname))', I have an index defined as alltrim(upper(fieldname)). I did this because I read that the optimization will be turned off, if the indexes are altered.
>
> - I have avoided the use of $,At(),Empty() functions.
>
> - Most tables have 4-7 indexes defined.
>
>After making these changes, my quries take longer. I am trying to find out why this happens. Any help would be much appreciated.
>
>Thanks in advance.
>
>Ria