>>Hi Naomi,
>>
>>>5. In one of the table we have about 20 or more indexes. About half of them use the exact same index expression, but different tag name.
>>
>>ASCENDING/DESCENDING is an attribute you've found out already. Two other frequent differences are FOR filters and collate sequences.
>>
>>Filtered indexes often are introduced when you need to display the entire table in a grid, but need to filter on simple things such as "only printed invoiced", "hide archived records", etc. Since the grid wasn't Rushmore optimizable for a very long time, a filter on the index provided a fast solution.
>>
>>Collate sequences become important when you need to sort foreign data in their native sort order. Hence, you might have on index with MACHINE for searching and Rushmore optimization, and one with COLLATE for displaying data in a grid.
>
>All indexes in that table use MACHINE collate (luckily).
>
>I have another question. The form in question has all complex logic of setting filter, etc. in its Activate method. It makes the debugging of this form much harder.
>
>Do you know what may be a reason for this and do you think it would be OK to move the code in the Init event?
>
>Thanks again.

Activate gets fired every time the form gets focus. The only reason I could think of is if the filters where based on a global var and another form changes the global var when they go back to this form the Activate would change the filters on the tables. If that's not the case I think moving to the init would work. You could always move it to the init to debug then put it back in the activate once you found the bug.