You are really limited by the resources of the server machine - consider that each user will need around 60-80mb ram for a session.

There are other things to consider as well from a general design standpoint - you may need to make sure that your application is set to use resources specific to the current user. Ie, just having a c:\temp directory may not be a good idea since there could be numerous people in the system concurrently.

Also, if you use the registry, be aware that each user gets his/her own copy... so you will need to store things at the local system level so everyone can access them.

There are a lot of other things as well - I did this in the past, and had to really work on a vfp5 application to get it to run on the same machine concurrently. But it can be done, and is a great design. I actually implemented my vfp app to run in the browser (using citrix)... was very neat, and did not require the use of the terminal client.

HTH
Wayne

>Does anyone know what a "reasonable" number of users connected to TS over the internet would be. My VFP app is a data-entry type of application that wouldn't be very transaction-intensive, but some of the tables are in the 150 - 250 Mb range. The server hardware would be new and up to "today's" standards, (whatever that would be today..)
>
>We are in the "what could we do" stage to host an app in-house for clients around the US on our servers, and eliminate the need for branch-office upload/download transfers to merge databases.
>
>Of course SQL server comes to mind, but we would probably develop a Web-app with a VFP back-end before going this route.
>
>Any knowledge in this area would be appreciated, Thanks!