The first thing you need to understand is that there's no magic bullet in converting an existing application to run over the web. Here's a pertinent section from our FAQ:
Because of the nature of the World-Wide-Web, there is no way you could take an existing FoxPro application and just get it to run over the web. Web browsers receive information in a language called HTML (Hypertext Markup Language) and send information back to servers using HTML forms. In order for FoxPro to communicate with web browsers it must be able to read the input of HTML forms, and format its output as HTML text. For this reason, the input and output routines of existing applications will have to be re-written. Other procedures handling the logic of the application, (e.g. queries, data-updates, etc.) can remain as is.
In some cases existing reports can be used without modification, by re-directing their output to a text file and then sending it to the browser (<PRE> tags have to be added at the beginning and the end of the text). This method works adequately if you have a large number of reports that you want to convert in a hurry, but the output appears just like an ASCII text dump with no formatting. If, on the other hand, you want to have aesthetically pleasing reports that take advantage of the HTML formatting tags, you will need to either include these tags in the reports, or use a different method to create HTML output.
It's actually not very hard to create a simple web-based application, as long as you understand a few things about how the web works, including HTTP and HTML (there are other acronyms that I could throw in there, but these are enough for you to develop a simple app). I recommend that you start by installing FoxWeb, reading some of the documentation and examining the ContactMine sample. The latter should get you in the right direction and offer you something to play with. Several of our customers have used it as a starting point for their own applications. Along the way we are here to help you with your FoxWeb-related questions.
Normal FoxWeb pricing is per-server, which means that for an Internet-based software as a service (SaaS) offering you are paying at most $249 per server/site (or less with volume pricing). We don't have a bundled unlimited offering, but do offer steep volume discounts if you want to include FoxWeb as part of a software package. Please contact us at firstname.lastname@example.org for details.
FoxWeb Support Team
Sent by Gary Mattox on 02/05/2012 11:49:03 AM:
Okay, I have been developing in FoxPro/VFP since it was FoxBase. This is the first I have seen on FoxWeb. So, here's the question. If I have an application that I want/need to put on the internet. It is written in VFP9, has about 50 forms/programs and 40 dbf's.
Will the forms look the same?
Do you just wrap the app in html and compile through FoxWeb?
In other words what kind of effort will it take?
It would be great to see a FoxWeb app example of a complicated VFP app conversion. Where I could evaluate the effort it would take. And maybe a VFP business app that is "live" on the net.
Finally, what costs would be involved if this is a business app that you sold as a standalone intranet app or as subscription based on the internet.