>Zlatin,
>For VFP 6 SP5 and VFP 7, don't forget that you can just call VFP mtdlls from ASP and ASP.NET. We prefer doing it this way since you can take advantage of the technology Microsoft is putting it's muscle behind and still use VFP code. It has a lot advantages over FOXISAPI including: less complex to install and distribute, stronger objects and methods to manipulate web information(ASP built-in objects), just as fast as FOXISAPI (since ASP.DLL is just another ISAPI extension), and blends in very well with existing ASP and ASP.NET sites...

Just will cite myself:
>>After making all the trade-offs you will have choosen a technology:
>>
>>If it is Web&Windows based it is supposed to be some kind of IIS extension: ASP, ISAPI, etc.
>>
>>As it is supposed to be a database application - maybe with SQL Server backend.
>>
>>As it is based on an existing VFP one - it may use COM together with FoxISAPI or you may rewrite it to use Web Application servicies that are part of VFP7.

I have not removed ASP as an option. However if anyone chooses to use ASP he will need to program part of the application in VBScript. If someone uses FoxISAPI the entire app can be in VFP. ASP stronger than VFP?!
Anyway...
In both cases there may be encountered need of client scripting in ECMAScript (formely JScript&JavaScript) or use some other client extensions - Java Runtime, CLR, etc.

Kind Regards