Charlie,

>Does it cache network data? It would be problematic. Since my last USE, the table structure, CDX structure, and all the data could be different.

VFP can cache networkdata. Actually it's the workstation that can cache network data. On a NT network it is possible to cache read and writebuffers for shared files, given you're the only one using this table. It's a kind of exclusive mode while you opened the table fox shared access. From the top of my head, it's called Exclusive Oplocking. Another feature is that a NT server keeps the files open for a while on the serverside in case you'll open the table again shortly after you closed the table.

Given these two features, it *could* make a difference. Though this theory, I never tried to examine this behaviour in detail. A simple test I did with a client: I did a replace on a 10.000 records shared table over a WAN, while no other users were using this table and another replace with other users accessing the same table.

The difference in performance were really huge. In the first case it took less than 30 sec to complete. The second one took about 8 hours.

I can't judge, if it would make any difference on your test, but it could be wise to take them in consideration.

Walter,