>>
>>Did you test with an index set on the table?
>>
>>Thanks for trying to help me diagnose.
>>I have done some further testing myself.
>>New form (base form). New grid (base grid)
>>add table to DE (125,000 records, 86 fields) with order (this is important) set to main index
>>set grid's datasource to table.
>>added three buttons to the form:
>>
>>button1.click:
>>temp = seconds()
>>go top
>>thisform.mygrid1.refresh
>>thisform.caption = str(seconds()-temp, 5,2)
>>
>>button2.click:
>>temp = seconds()
>>go bottom
>>thisform.mygrid1.refresh
>>thisform.caption = str(seconds()-temp, 5,2)
>>
>>button3.click:
>>temp = seconds()
>>go 60000
>>thisform.mygrid1.refresh
>>thisform.caption = str(seconds()-temp, 5,2)
>>
>>clicking button 2 changes the form's caption to .04
>>clicking button 3 changes the form's caption to .01
>>clicking button 2 again changes the form's caption to .02
>>clicking button 1 (go to top of table) changes the form's caption to 2.36
>>
>>Any idea what's going on? anybody?
>
>I used an index set to ingrid search field. Without setting manually you should use Rushmore optimizable expressions and instead of go top and go bottom (these do it sequentially) use locate or seek "" (for go bottom use the index desc.).
>Cetin

Ok fine. I reconstructed the test to use first seek ("A", "M", "Z"), and then locate for("A", "M", "Z"). Same exact results. This has nothing to do with search method, Rushmore, or indexes. The delay is being caused by the grid refresh. (I have tested SPECIFICALLY for this).