Hi ed,

>The problem is that the limitation is bandwidth; your typical LAN transmits data at 10Mbps-100Mbps, which an ISDN link may have a bandwidth of 128K. VFP executes client-side; any evaluation done by the program requires that the data move over the wire from the server to the client, and that the client perform any processing. If your netywork permits client-side data chaching with a reliable mechanism to validate the cache before a reference to the cache is used, then a .5Mbps link may perform reasonably well; if there's no caching, data will move at most at 1/20th the speed it moves on a 10Mbps (standard EtherNet); if the cache is not validated before every reference, you risk an invalid cache data state. Win2K Server provides mechanisms for client-side caching with verification; this did not exist in NT Server, and AFAIK, is not provided except in the Win2K and .Net servers (ie peer-to-peer doesn't handle it AFAIK.)

Are you talking about opportunistic locking, or another chaching mechanism ? the buffering modes via opportunistic locking do exist in all Windows versions I know of.

I you're talking about something new, where can I find information about that one ?