Hello, >SET ORDER, SET FILTER All orders are set to 0 before querying and no filter is in effect. >Also, the amount of memory you have available, probably less in the application, than when run alone from a prg. Perhaps, but I'm not sure... Honestly, I doubt that less amount of memory can cause such slow down of the speed. Really, it causes approximately two times difference in speed. Very strange.... I tried to open the table (100 megabytes in size) 20 times and then ran the query from prg, but the results was the same (more speed when it runs from prg). >> Can anybody tell me which SET can affect query speed (I know SET >> Optimize)? May be there are some other SET that can slow down query? >> I'm asking this because when I run my query alone in prg, it takes around >> 60 seconds for first time and then around 38 seconds for subsequent runs. >> But when I run the same prg within application, the first run time is 115 >> secs and the subsequent calls takes 68-70 secs. Obviously, something >> slows down this query.