>>Also, VFP does not take whole index to memory, if it would be so, it just could not work with large tables on network.
>
>When i took a second look I did come to a more detailed conclusion. Rushmore must have all the index records regarding the resultset in it's memory to work. If it cannot load all the index records rushmore will not work.
>
>Documentation Developers Guids FPW 2.6 Page D17-2
>
>Walter

It seems to me that it mostly about the known problem: where temp file exists (in RAM or on hard drive). When VFP runs multi-step queries it seemingly applies lots of temp indexes, i.e. create temp recordset on first step, then reindexing this recordset, creating another recordset and so on. Obviously, that this process will go much faster, if everything is in RAM.