>WWWC basically has it's own ASP style engine and you can run code inside of that page. So why bother with ASP, or alternately why bother with WWWC in the ASP pages? If you need any Fox code access use the WWWC scripting which is like ASP code, except it's Fox code. If you don't need to run Fox code use an ASP page.

I need to benefit of both. Basically, the template is having a FILETOSTR() function which is including an ASP page. In that ASP page, I have a lot of ASP code. So, the template contains a lot of VFP code and that templates includes an ASP page. So, the result would be that the content of the ASP page will only interpret the HTML code and not the ASP code.

From Visual FoxPro:

1. lcHtml=Response.ExpandTemplate('Myfile.html')
2. Response.Write(lcHtml)

Myfile.html is a template which contains a lot of fields from an HTML form. So, at this point I have all my fields to be ok as they include the values from the table. That page also includes some VFP code. Everything is ok at this point.

Myfile.html contains FILETOSTR('Myfile.asp')

In Myfile.asp, I have some HTML code and some ASP code. The HTML code is interpreted ok. But, the ASP code is not as the ASP code is not recognized by the WWC. Well, it may be but I just don't know how to achieve that. I guess you have a function to call somewhere which will make that happen.