>>>The table HAS to have an order set to see these results. I can't think of a single grid that I have in use that doesn't need the records in any particular order. To order records in a grid, I have to set the index. If this wasn't a requirement, I wouldn't have a problem. Can you please run your test with an index set on the table?
>>>
>>>There is not filter on the cursor. I have an index on deleted() and DET DELETED is ON.
>>>
>>>I don't understand why you are suggesting scenarios to slow the grid down...
>>Hi,
>>I set the table to another tag than searchfield and to one same as searchfield. Results are same.
>>Grid refresh were instant in both cases again.
>>Table I used for test was a copy of customer.dbf with 167808 recs, index on upper(contact) and company.
>>I told those scenarios, to remind you of possibilities slowing down a refresh.
>>I don't want you to use them, just trying to help.
>>Cetin
>
>Well, this I don't understand. I appreciate your efforts in testing. It sounds like we are testing the same scenarios, but getting different results. I think I will call MS to see if they have any insight on the problem. thanks.

I know this may be time consuming. But to really test and be accurate you would have to have the exact data, and form code. Is this possible? Could this possibly be a hardware issue?