If you want to use FoxWeb to authenticate users, you will also have to serve the protected content with FoxWeb, which works great in most situations, but is not the most efficient method for heavily loaded servers, or for protecting very large documents.  FoxWeb runs outside the IIS process, so you will get better use of resources if you don't force static content to be served via FoxWeb scripts.  If you do choose to use FoxWeb, then the Returning Content to the Browser topic of the FoxWeb documentation contains information about serving non-HTML code with FoxWeb scripts.

 

An alternative would be to use one of the 3rd party products that install themselves as ISAPI filters and can either use their own internal database, or connect to an ODBC data source (including a VFP table) for userid/password information.  One such product is AuthentiX by Flicks software.