Andrus,

I guess I'd try converting their query input into a SELECT instead of a filter and create a cursor. Fox will have to scan the whole table for either a filter or a select unless there are indexes to support rushmore optimization. I've never had to be concerned about Fetchsize so I don't have any recommendations there.

>Users can construct an arbitrary query from
>large single table using query builder.
>
>Parametrized view cannot be used in this case since foxpro scans
>the WHOLE BASE table, when query returns many rows and this takes
>TOO long time. It is stange that Fetchsize parameter seems not
>to work !? It must work with local views also ccording to fox doc.
>
>Linkmaster property requires that there must be a parent table and
>existing index in child table.
>I don't have a parent table (it is strange to create dummy one for
>query). Also, for user-defined arbitrary filter contition it is not possible
>to pre-determine reasonable index in child table.
>
>So it seems that there are no solution at all.