>Is there any way round this problem using your 'framework'?

Not without doing anything too overkill. You could write your own though.

Here's how I'd do it. Create the HTML Pages right in DreamWeaver and use the directly. Then, to do the standard Header and Footer stuff, use the ASP include tag (there's an example with my lecture at the WIki).

That takes care of the standard look, now for the editing. You could write an ASP Page to load an HTML file into an Edit BOx and save it back using the File Script Object. For the FSO documentation, check this out: http://www.msdn.microsoft.com/scripting/default.htm?/scripting/vbscript/doc/jsFSOTutor.htm

>Also, I get the impression the fastest solution is to have as few objects as possible within the .asp page itself, and call as much HTML as possible from the VFP COM object between the % % delimiters. Am I right in this assumption?

Yeah, everything you call puts over head on the procedure. This calls, less overhead.