>>>>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).
>
>Hi,
>If search time has nothing to do with this (all are fast)
>then could it be something like *set deleted on* and no index on deleted(),
>some of grid columns controlsource prop are set to udf() or something like activerow,
>filter etc ?
>Especially if you have a column with controlsource = this.activerow then refresh would be so slow.
>Cetin

All of these scenarios would effect search time, not grid refresh time.
If this was a problem with optimization, it would affect ALL seeks, locates, etc.
But it doesn't. It only effects one. It only effects any effort to move the pointer to the very first record in the cursor, and refresh the grid. Whether I use GO, SEEK, or LOCATE FOR, or which index the statement uses, the results are the same. I am confident that you can reproduce this behavior if you perform the test that I described above. The tests I have run are with base forms, base grids, and simple commands with no funky indexes or anything.