Pat,
There's probably articles in Advisor and the other mags about the techniques and products, but, here's a quick breakdown for using VFP and the web:
1.) FoxWeb, 3rd party, oldest, emphasizes scripting VFP within HTML pages
2.) ActiveFoxproPages, 3rd party, uses FOXISAPI, emphasizes scripting VFP
3.) Web Connect, most comprehensive and complex, most difficult to learn
4.) FOXISAPI, least supported, complexity in setup, random errors
5.) VFP MTDLLS with ASP/ASP.NET, most supported by MS with strategic direction(.NET, web services). Natively supports all of the technology as the others including scripting(EXECSCRIPT).
I favor #5 because it takes advantage of most of the core MS functionality and ease of setup and use. Also, unlike the others, #5 does not have a separate .EXE server that has to be maintained and hacked to run as a system service (for running when logged off). This addresses your question about keeping it running...
>Greetings,
>I am looking into allowing access to a database through the web (intranet). I have encountered numerous products related to this and have read a lot about the concept so I think I know the basics. The question is then, has anyone reviewed the available products for different applications in different situations?...Or how did you select the one you are using?
>
>The only big restriction I have is that the application is for a client company which means it has to to somehat easy to configure and keep running on a server without me around all the time.
>
>Thanks,
>Pat