>Yes , this is for the stock market application i am using for my personal ends. It is a new parameter called Noise of the data ... the most number of price ranges in the period... I even thought abt adding the whole years data and saving the cursor but it kills the basic logic of the noise for the period ....
>
>also in case i do use it by having many cursors like each for the 80 values... there would be lot of unnecessary over head suppose 400 records ??? then the number of cursors would be 400-80 = 320....

I have some trouble visualizing your layout - you need one "foo" table for each stock for each window of measurements (the 80 days or hours or whatever) to replace the part of code aleady shown. Since the 80 is hardcoded I guessed it to be a constant number. If you research more than a couple of hundred stocks, create a table for "noise" with a key added for the stocks - instead or creating a empty cursor work on the records for that stock only. Even reading the records for one stock into a temp cursor, correcting there and saving back into the table/cursor for all stocks should be faster than your current approach. But having data for all stocks in one precalculated table:

removes the time to create tmp cursor
removes the time to index tmp cursor
removes the time of roughly 78/80 of the replace operations you currently have

when replacing:
- adds some mimimal time if using rushmore because of larger cdx
- should take minimal time more for seek, same time for replace (using Craig's faster method)
- you could check out set key

HTH

thomas