>There is a network contractor who claims that on a local network, when FPW2.6 accesses data,( like when doing a select) accessing data on the server from a local computer, the data is cached in Memory ON THE Server! This causes the server to require a lot of memory for data intensive programs.
>
>I have always believed on a network that Fox creates its temp tables locally as well as cache's all the data locally in memory.
>
>Could someone please shed some light on this.
>
>Thanks
>

Bernard,

It is possible that the network OS is caching stuff in memory on the server but that has nothing to do with FoxPro, it is how the server is configured. If the server is set up to optimize hits by caching stuff in memory then the network guy is probably right that data intensive stuff uses RAM, but that is because data stuff has data to be cached.

Your friendly local word processor would only be caching a single document and that doc does not have interactive updates and fetches going on, because it is not a database application.

Now if your network guy is blaming your application for using server resources I would tell him to take a hike and get his server configured correctly for the requirements of the business's applications. IOW, if the server is bogged down beacuse it is being used the way the business needs it to be then the network guy really has to optimize the configuration of the server to best meet the business needs. You can always add more RAM to the server (which would cost the business far less than rewriting a database application so it doesn't use "too much data").