You might get better interoperability by using VFP mtdlls that are called by ASP. For example, you could start by just packaging those VFP routines that need to interoperate with ASP in a VFP mtdll and call it from a .asp that has the INCLUDE...
>When a page is returned by WWC, we loose the ability to benefit of ASP functionalities. For example, whatever is pulled from an ASP page on the Web site can include commands such as INCLUDE. However, that same INCLUDE command won't work if the page is generated by WWC. So, I have to paste all my code from that page into the page which has to be generated. Then, when I want to make a change in that included page, I have to think of also doing it where I pasted the code.
>
>Is there a way to avoid that?