Emmanuel and everyone,

VFP does NOT transfer the "whole" index over the wire, It gets what it needs.

VFP with large tables can out perform any C/S backend I have ever seen. The keyword there is "can" and not does. If the VFP code is written correctly and the correct indexes exist on the data and the network cable is not saturated by traffic and the server is not bottlenecked with work, then VFP can outperform the C/S bakcends.

Table size if often quoted as one of the reasons to go to C/S as is performance. These two issues are NOT sufficient motivation for VFP developers. VFP developers should first look into what they are doing that is slowing VFP down.

The major reasons that hold water for VFP develoipers to make the move to C/S are;

1) More robust security on the data
2) Accessnig data from diverse applications
3) Robust transactrion servicing
4) automatic live backup of data
5) The company is going that way

Performance and table size are not among those reasons.