>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?

I have a subclass of the wwResponse object that I use in each WWWC project. This subclass contains custom methods that are specific to the project that return chunks of HTML that might be common across pages. This allows me to do things like:

Response.CreateMenu()
Response.PageFooter()

or any number of things in between. You can abstract that even further by storing your HTML chunks in htm files, and having your custom Response methods do something like:

FUNCTION CreateMenu
  THIS.Write(FILETOSTR("mymenu.htm"))
ENDFUNC