So, you wrote an HTML parser to handle recreating your pages, including any reusable functionality? Now your talking my language. <g> Ok, that's an interesting approach. Not sure I get your use of #includes to generate the final versions.

>Jay,
>
>Locally to run it you have to have installed IIS and have it up and running for ASP to work. I believe the same is true if you are trying to use ASP.Net.
>
>I can tell you that working in ASP is kind of a pain at times with the way you have to mix HTML content with the VB code to dynamically generate those parts.
>
>There are other options like PHP too.
>
>Whatever you decide your ISP will have to allow and support.
>
>If you don't really have dynamic content (on a sort of per click basis) you do have an option of generating your website from VFP code. That's how I build the Q&A portion of my VFP site. It's pretty easy to write code to parse your base HTML pages and do #includes to emit final versions of the pages to another folder and publish them to the webserver from there.
>
>>Ok, good information. If my only real option is ASP, then what is the easiest way to implement that? I'm guessing first thing is that the provider's server has to support ASP extensions. Can I setup my local PC to interpret ASP extension so I'm able to test my code? Will everything I normally use in an HTML document work with ASP extensions?