Hi Sally,
AVFP uses either ASP or ASP.NET to call vfp mtdlls. If ASp or ASP.NET is already installed then there is no ISAPI to deal with at all. Also, if the AVFP web app uses the native VFP database, then there are no extra Db issues to worry about. Please feel free to use this forum for tech support.

>>> I'm not sure I understand why she regards AVFP as difficult to maintain. Is there any way we can clarify this? If the AVFP web application is using the SessionTable object then this might be the reason since a Memo field is being used for session state and would have to be maintained. Using the "Session" object, however, would solve this since it uses no Memo field and is actually much faster.
>Regarding memory consumption, it has to be remembered that VFP contains a database manager. To compare it with .NET, you'd need to include .NET plus either SQL or MSDE to arrive at a reasonable comparison with VFP. No doubt VFP's memory footprint would actually end up being much smaller...
>
>This is in production environment.
>The technical specifics is that this is a Fox + ISAPI + Database website.
>
>From hosting VB-ISAPI, CSharp-ISAPI and other websites, there is lots of support time required to handle support requests.
>
>For example, locking error, database connection error, server-down-time, email handling, web-page errors.