Hello Dennis,

>Is it just me, or is there NO WAY TO MAKE A ASP PAGE USING VFP?

I have to disagree with you since my current project is doing exactly what you are implying can't be done here. If you don't think VFP has a place in a Web application, maybe this makes it clearer:

I have data going to and from a legacy system (AS/400). I need a web interface to this data.

Here's how VFP with ASP makes this very doable:

-Create a VFP COM component to interface with the database.
-Create ASP pages(which aren't much more than HTML pages with embedded server-side scripts) that create instances of the VFP component, and use its functionality.
-Create an SQL Server database to catch new data, for new functionality, and link the AS/400 data into this Server thus giving the application a single data store.
-Create Stored Procedures in SQL Server to provide additional interfacing with the legacy system, and promote consistency in the middle-tier.
-Create methods in the VFP COM component to do all things you would do from a regular application in VFP (read in data, loop through and process records, do lookups, etc.)
-Call these methods in your server-side scripts.

This is just straight n-tier type programming, and this IMO is exactly what is meant by VFP in the middle-tier. Yes, ADO could be used to do this directly from ASP, but VFP's data manipulation capabilities make it very attractive for this kind of stuff IMO.

In general, I think the exams focused on VFP in the middle tier, which is what everyone was saying they would for months up here. In short, VFP is no longer envisioned by MS as a file-server app dev language, it viewed as a middle-tier COM component language.

So to answer your question, "is there NO WAY TO MAKE A ASP PAGE USING VFP?" my answer is creating the pages isn't the question (ASP pages are textfiles, and yes VFP can generate HTML rather nicely). The better question is: "does VFP have a role in an ASP-centered web application?", my answer is a resounding YES!

HTH
Bill