>>However a colleague has been testing it across the company's
>>WAN with a view to centralising the database and we are
>>experiencing dire speed problems.
>
>To really perform well with all its GUI/data controls (such as grids, filters, etc) VFP needs to run on a network with abundant bandwidth. You can re-engineer some of your app such that less continuous network traffic is placed though the bottleneck you are facing (might be your Lan/Wan bridge, might be the Wan itself). For example, rather than Browsing a table on your server, instead do a Select-SQL on the table using a Rushmore optimizable WHERE clause that will retrieve a limited result set based on the user's parameters. Then do a BROWSE locally on the cursor that is returned to you. Create indexes for everything you will be using for lookups. Doing table scans with file server apps like VFP take up huge network bandwidth because your local app basically has to transfer an entire table over the network whenever you do a table scan.
>
>A more elegant solution, if you really want an unlimited WAN implementation (i.e., scaleable to global use over the Internet), I would recommend considering a Web database solution using VFP as your database engine. This approach is part of a growing universal thread, you know.

Agreed, but until then copy the apps to a local drive and ensure that your temp files are also handled locally.