John,

Your application may well be a good candidate for SQL Server. However, you may have to re-work the application signficantly. This is especially true if you haven't made heavy use of views and/or SQL commands in your application.

WinFrame or Windows Terminal Server might be your best bet. There are hardware and software costs (as there would be with c/s, of course), but your application would probably run as is. VFP is slower than most apps under WinFrame because it doesn't use standard Windows controls, but with the bandwith you're talking about you'd probably get decent performance.

>
>Here's the deal. I have built a multi-user file server based app that controls membership and marketing data. All of the data is located on my NT Server and the app is lauched be each user from their local PC. We are connected to several other sites via WAN (partial T1 384k or so). The tables are quite sizeable 150MB and up with some smaller lookups as well. This apps main purpose is to mail contracts and letters and to track membership information. What would be the best approach to allow access to users in other sites that are connected to my network? I've played a little with Citrix and haven't ruled that out yet, but as you said, learning SQL Server is "a good thing for the longer run". I respect your opinion as well as many other seasoned programmers opinions here on the UT, and would ask you how might you approach something like this. Though I would like to learn more about C/S, now is not the best time for me to hunker down and learn another product.
>
>regards,
>john.