>>>Matt,
>>>
>>>From what I know from the documentation, the less you 'SET' the better the performance. I specifically remember this about ORDER. I also suspect that rushmore exclusively recognizes .CDX, and simply disregards .IDX. In fact, if you want to increase performance, and robustness to a certain extent, I'd advise to changed the .IDX into .CDX tags.
>>>
>>>HTH,
>>>
>>>Marc
>>
>>
>>Agreed, and done...to a certain degree. Legacy app. Some optimization was done by adding CDX's, but the old IDX's must be supported or else a major fix is necessary and we're rewriting it in 5.0 anyway (it's a FPD2.5 now)
>>
>>Thanks for the clarification on the SETs. Perhaps I was confused by the use of IDX's in some of the older apps I've worked on.
>>
>>Matt
>Matt,
>
>IDX's are used by Rushmore if they are already open when the table was used. Any index with a FOR clasue is NOT used by rushmore at all.
>
>SET RELATION has little or no affect on SQL, it may speed itn up because the SQL engine will do a USE AGAIN instead of a USE which is slightly faster.

But in this case is not the relation the one who speeds things up, but the fact the tables are already opened, isn't it?

Vlad