As Frank just mentioned, the problem may lay in the way the VFP mtdll is being called. Here's what I have in C#:

< % @Page Language="C#" ASPCompat="true" %>
< % @Import Namespace="avfpdemo2_dotnetproxy" %>
< %
server x ;
x = new server() ;
try
   {
	Response.Write(x.main());
   }
catch(Exception ex)
   {
       	Response.Write("Caught .NET exception, source: " + ex.Source + " message: " + ex.Message);  
   }

%>

Please let us know if any of this works!

>We've written an asp.net application with fox pro dll's and foxpro dbf's. The dbfs run on a data server along with foxpro.dll in COM+. On the web server we have the application proxy for the foxpro dll and the asp.net application. Everything runs wonderfully with a couple of users, very fast. When we put around 11 users on it, it ran wonderful for about 5 minutes then we started getting errors on the COM objects.
>
>here is an example of an error,
>
>Server Error in '/k_webab' application.
>
>Public member 'functionName' on type 'Iclass' not found.
>
>(the errors are random, not just one or two functions)
>
>These functions are there. They work fine in a single user environment.
>
>I fiddled around with Pooling and Recycling in COM+ which seemed to help, but we still get the same errors.
>
>
>Anyone ever have this problem?