>>We have a VFP 3 application that's not client server. Speed is acceptable considering all 50 users have 32 MB RAM machines and that we recently upgraded our file server. We'd like offices in other locations to be able to run the app as well? What are the requirements to allow it to be accessible from a browser as well? Does it have to be client server or three-tiered?
>
>Three-tiered I guess. :)
>
>>I attended the MS Developer Days conference and my understanding is that to deploy your app through the internet, you'd have to have a "VFP Automation Server" which is responsible for business rules, dynamic generation of HTML pages, retrieving data from VFP tables and sending back the built HTML page (with the VFP data in it). What the automation server does is read the VFP form's objects and translates the form into an HTML looking page. To deploy the app over the internet, can we just use the existing app as the "automation server" and then add logic to dynamically build HTML pages based on the forms as well as other web related procedures?
>
>The automation server is one way. As for your question, I would say yes, but changes will have to be done in your existing application to be Web aware.
>
>>Can you point me in the right direction? Also, there is a second phase to the existing app we're using. How can we write it such that it will be easily migratable to a three tiered app? If we use local views, how slow will the app be. At this time we cannot afford SQL Server or Oracle.
>
>If you didn't have a need for Client/Server, you won't have a need when moving to Web. You can continue to use your tables as is.

*************************
Thanks, I guess we'll just keep on writing the way we've been writing and worry about deploying over the internet down the road. I just wanted to make sure that we won't have to scrap and start from scratch.