Thank you for the reply. I need to clear some more doubts before I can propose the solution to my customer. My customer is very fussy over the response time. They want me to give them a estimated improvement in respond time before they are willing to change. I would appreciate if you can give me an idea..

The client server application will be running on 2 LAN linked through a leased line. Roughly what is the speed difference will I experience on the local LAN as opposed to the remote LAN. If the data queried is less than 1K, am I looking at a response time of less than 3 seconds? At the moment, if I run natively, I will get the data within a split second on a local LAN. From your experience, what is the response time for a simple query of less than 1K of data over a leased line?

By the way, I should correct myself over the '400m distance'. It should be 10-20 km.



>Either of the choices you suggest should work. 256K should be sufficient speed for a well designed client/server application. Certainly the configuration could affect the speed. The time to open the spreadsheet seems slow, but not completely out of line. Regardless, there's no way you'll get good performance accessing FoxPro data natively over a 256K line.
>
>>I have a VFP application running on Novell 4.1 netware. Recently, my user tried to run it across a 256K leased line to an office 400m away and find the speed unacceptable.
>>
>>I am considering whether to upgrade it to Client Server OR run it separate and do a batch update each day.
>>
>>From your past experience, which is more feasible?
>>
>>Also, can the slowness cause by wrong configuration? I tried opening an Excel file (1.79M) in the server and it takes 2.5 minutes as opposed to 2s on local.
>>
>>Thank you.