>>..., but there is still the overhead of firing up the Fox COM object on each hit, adding a bit to the overhead. As Rick said, that's where the speed differences come into play.
>
>And this may be changing, I would bet that MS is working hard on making ASP/COM development premiere beans. I can't tell you with any proof though, just FWIW.
>
>>Running WC projects under ASP-compatibility mode is a step backwards, unless performance and responsiveness is not an issue.
>
>I never used it, I don't have 3.0. I just read and assumed that he changed alot of the syntax to be directly the same, and make it so switching between the two would only require a middle tier type procedure. That would be pretty handy.

Actually you make no changes whatsoever. You simply create a new project (you need a new ClassID) recompile it as an MTDLL and load a special loader ASP page or load the new Component directly from an ASP page.