Hi Randall,

You should check up on Rushmore Optimization in the help system. Find "Rushmore technology" in the index, and then select the subkey "optimizing expressions"

The reason why it gets slow sometimes, is because Rushmore decides that it cannot optimize your query to use indexes, and then makes a full table scan. The order of parameters in your where clause is very important.

Cheers,

Peter



>I have noticed that if I use a SELECT-SQL like:
>
>SELECT * FROM TABLE , I get the result pretty fast. When ever I complicate things as in:
>SELECT * FROM TABLE ;
>WHERE BETWEEN(DATE,DATE1,DATE2) AND INLIST(TRANCODE,'26','27') ;
>INTO TABLE2
>
>Things slow down to a point wher you think it is never going to get the data I requested. all of the tables of the tables are out on the network server. I have noticed that sometimes it makesa difference if I bring the results tabel over on the users PC. Any way to get around this problem? I have indexes on the tables for that items I usally ask for. I read somewhere once that you can open and order the table ahead o time and it helps the SQL do it's thing. IS this true?