>>When this form runs, the grid will appear extremely slowly. It seems that
>>FoxPro will not use index in grid refresh: it scans the whole table. Also,
>>when user presses up/down arrow in first/last row, this scanning begins again.
>>Therefore, FoxPro cannot be used for data editing in a table.
>>Maybe this can be resolved using local views, but this requires using a database, but my table is for compatibility reasons free table?
>>Maybe the following trick helps: adding a dummy non-visible master grid to form and making dummy parent-child relationship. However, child grid order cannot be controlled if this is used?
>
>Three ways to speed this up,
>
> 1) SELECT Document
> SET ORDER TO DocType
> SET KEY TO "A","A"
>
Thank you very much for this suggestion. It is really genious.
It is intresting that the syntax with range without RANGE clause
is not documented in vfp 5.0a foxhelp.hlp file in SET KEY syntax
description.

I think i will try to use the "parametrized" SET KEY command

SET KEY TO RANGE m.doctype, m.doctype+chr(255)