>>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.

Hi Erik,
I came to a deadend.
I ran another test with 167808 recs. Grid refresh was instant with the first, last and middle recs.
Order was set to none and only one index on searchfield, no special controlsource and relation etc.

-Consider a udf giving running totals
-Delete 2-20000 and try *set deleted on* with no index on deleted() and then with a dummy index on it.
-Try activerow as a controlsource (beware to try on a small set or you'll need a coffee break).
Especially this one has nothing to do with search time but grid refresh time.
-Try set filter also (with and w/o optimization).
Those scenarios in fact are not only related with search time but also grid refresh time as well.
Cetin