Hi Rodolfo, Take this with a little subjectivity from me :-}... >1) Between FoxISAPI (free with VFP) and the commercial products: Is it just a matter of scalability? FoxISAPI is more like a demo rather than a full product. It implements the Web interface but that's about it. It provides almost no Web specific support in Fox code. It works and it's fast, but it's difficult to debug because everything happens within the Automation context and a compiled EXE. The latest version (the features of which weren't available when I wrote the FoxISAPI article) does provide better scalability via a pool manager and limited 'online' debugging with a debug mode that runs VFP interactively as an Automation server. I'll let the other 3rd party companies speak for themselves, but Web Connection provides a ton of functionality on top of the basic Web communication layer, including server management (starting stopping servers remotely, updating EXEs on the fly, keeping people out during maintainence operations etc.) built into the ISAPI DLL. Applications can be built interactively in VFP using the standalone development environment, and then be deployed either as standalone applications or as Automation servers for best performance all with a single #DEFINE switch and recompile. Automatic hit logging plus reporting on server status and the logs; error logs, email notification on errors, full suppport for SMTP, FTP and HTTPGet. That's the system stuff... In addition WC provides an extensive VFP Web application framework with a series of VFP classes that provide both low and high level control over building dynamic output. The wwServer object handles incoming requests, the wwProcess object handles a specific 'application', the wwCGI and wwHTML objects handle input and output to your application. It's a framework of objects working together to make easy work of the Web interface so you can focus on building your application and not worry about the Web logistics. Your code gets control in one place (a process class method), and you can write a dynamic 'Hello World' request there with one line of code. There are utility objects such as a user tracking wwSession object, a rotating banner object, an object that can display full tables in either browse or record mode with a couple lines of code, the wwHTMLForm object that can render a VFP form on the fly in IE 4 (http://www.west-wind.com/wc.dll?wwdemo~IEGuest for a guest book app that's included with WC), abilty to create scripted HTML pages with embedded Fox code that are read by your application and much much more... >2) Between X-Works and West Wind Connection: Are they exactly the same type of beast or could it be tha you need one for certain types of development and the other for another types? I think it comes down to functionality described above. The concept is the same with all the tools - they provide the communications layer. All of the products provide good performance - enough to handle some of the busiest sites on the Web (this site running x-Works is a good example - Surplus Direct running Web Connection is another) with varying levels of scalability. +++ Rick ---