>We are talking of the process here. While the physical table resides in the server, the client will do all the processes in itself bringing down all the data across the network because VFP table is a desktop database. Besides, filtered indexed is not a Client/Server command, it's built in the table. That's why the first execution is slower although insignificannt because the second or third execution manipulates cached data.

Quite right - no disagreement on that - only that this is usually invisible to the user, and in fact, can be faster than true C/S. Your earlier response seemed to imply that vfp data could be slowed by pulling entire tables over the wire to the "client" machine when opened or queried...