Zlatin has a point about VFP not being a server app. Perhaps if you don't wish to upsize to SQL you could use a COM object that would run on the server forcing the processing to be done on the server and only pass back the results. Not sure if this is feasible in your position but just a thought.

Aloha,

James
>>One of my clients has moved the server with a VFP app to another building and installed a 512K fixed link back to the original site. Users at the original site are now experiencing major delays in accessing records (up to 3 minutes!) from an SQL query.
>>
>>The length of the delay suggests to me that the supposedly 512K fixed link is not transferring data at anything like that speed......or is a 512K link just too slow.
>>
>>Any ideas? If the link is too slow, can I modify the app so that it becomes a client-server one with all processing done on the server? Any documentation on this?
>>
>>Ideas/suggestions gratefiully received!
>
>Do you mean that you try to run queries against VFP table that is allocated on a remote machine with a speed of 512kbps?
>If so keep in mind that VFP is not a database server, so that entire tables are transfered on the wire when you query them.
>In that case I suggest to move to C/S (or n-tier) ASAP. You have at least two possibilities for upsizing:
>SQL Server (transactions, replications, stability, good tools for administration)
>MySQL (lightweight, limited functionality, low initial investment, may need additional maintenance, royalty-free)
>
>There are some topics discussing using Server back-end with VFP in FoxTalk magazine.
>
>HTH