>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!

IMO, 512Kbps is far too little bandwidth for a rich client app moving data across the WAN for manipulation at the client workstation unless the size of the data passed over the WAN is small, as might be the case for an OLTP system with a database backend and small active recordsets. With adequate power and memory on the server side and relatively little graphical content on the UI forms, a thin-client approach using WTS or Citrix MetaFrame might support a fair number of TS sessions running your VFP app passing UI elements between the thin client and the terminal server. You'll want fairly brawny terminal servers with multiple processors and plenty of memory, and tweaking the environment a bit with things like BITMAP=OFF, setting conservative buffer size limits with SYS(3050) and using storage local to the terminal server machine for temp file space often make a difference.