>>We have close to 200. Sometimes rebuilding the index files will cause dramatic improvement. How your application is structure will make a difference, ie. are you using views? Are your queries/views fully Rushmore optimized? SEEKS? Mostly new records? Mostly edits? Your network infrastructure can make a difference too.
>
>I think a good tip too is don't overdo it on indexes. I have seen some aps with 20 tags of more on some of the files... This actually causes more network traffic espessially with rushmore turnd on. Generally two indexs, a PK and a Candidate Key should be adequate. Other than that, use more order by and client side indexes.
>
>BOb

You have to be careful about how you create the WHERE clause of the SQL Updates from the View Designer. You could actually slow down the application even more if you don't do it correctly.