>Have you considered using Citrix/Windows Terminal Server. This would run your app exactly as it is now with no coding changes required.
>
>Unless you have a specific requirement for client server then look at this technology closely.
>

First, it's not my situation, and I'm well familiar with WTS/MetaFrame.

Second, there's a considerable expense in infrastructure to implement thin client solutions, like the terminal servers themselves and the necessary software licenses. If the existing workstations are adequate and the LAN is not a significant bottleneck, there's little compelling argument for thin-client solutions. In general, software that won't deploy under NT/Win2K at all elminates WTS as a platform, it requires considerably more administration than an existing network of Win9x boxes, and introduces new issues in deployment. It's not a panacea.

>Client Server could slowly be on the way out.
>

Burdening the terminal servers with heavy I/O can kill them, and deploying other server software, like IIS/SQL Server/SMS on the same box has a significant impact on the performance of the terminal servers. THin client doesn't make the need for C/S environments any less necessary; if you need the added services of of a database backend, nothing has changed; VFP still doesn't secure tables, implement a security model stronger than file-level access control enforced by the OS, and the data files are just as fragile.