>>>An alternative method to Paul's would be to use ASP to query the SQL Server directly and not use VFP. This would be the simplest route (maybe not the best though). From what I understand though (and what I have experienced) is that ASP becomes unwieldy when an application moves from simple to more complex.
>>
>>Could you expand on in what way ASP would be unfit for more complex applications? I'm just curious, as my own experience is quite limited so far...
>
>I am certainly not an expert in the field. My experience with ASP so far has been to build some queries against an access database (my ISP had problems with the VFP drivers). Vbscript is typed directly into the HTML page and thus there is no development environment (like with VB or VFP...). This makes it difficult to debug and test and also slows down coding since you are no longer in a visual drag and drop environment. I have liked it to Dbase II ... everything is interpreted code.
>
>Apparently InterDev addresses some of these issues, but I simply don't understand that product, so I could be missing something.

I believe a person can build complex applications and have been part of web sites that have done it.

There is drag & drop for building FORMS with ASP but not as sophisticated as VFP/VB. Also, load time for (example) dropdowns are longer then in VFP/VB so a developer must approach a form differently then in traditional EXE's.

As for debugging in ASP, run and crash, run and crash. It stinks when compared to VFP/VB. This is the only thing it has in common with dBase II. The developer must write their variables to the screen like in the old days (or as Cobol programmers still do it [g]).