Mike,

>(...)why should you know how Active Server Pages are supposed to [be] built in VFP...?

IMO this should be amended to read "why should you know how Active Server Pages are supposed to [be] built with VFP..."

I don't see VFP competing with Notepad(I use PFE, but you get the idea) on the creation of ASP pages, nor do I see it competing with VBScript or Perlscript, or JavaScript or (fill in your favorite ASP-supported scripting language here) for use in the page itself. Where I think VFP fits into the ASP model is a tool for creating ASP Components.

That said, I agree that on the desktop exam this seems extraneous, but the study guide does mention:


Create a COM component that implements business rules or logic.
Create a COM component that interacts with other components.


And while its implied that this is being done from within a VFP-only application, the mechanisms are *very* similiar in an ASP page, and using such an example on the exam again points to the de-vfpcentrification (cool invented a word there) in the MS strategy.

This also answers your original question, why do this? because that is the future of VFP (at least that's how it seems). Granted, I think of this as more distributed application development, but my guess is they used the ASP example to show its not limited to VFP-Only desktop applications.

That's been my mantra today, and I am sticking with it *bg*

Best,
Bill