Hi Steve,

I waited to respond until I could look at an article on Rick Strahl's site. It was down all yesterday. I wanted to see if he had any information to pass on about your situation. You shouldn't need to call ReleaseComObject. .NET will handle the reference count itself. Here is his article about using VFP COM components. I didn't see anything address your problem.

http://www.west-wind.com/presentations/VfpDotNetInterop/aspcominterop.asp


>Something new on this. I just discovered the ReleaseComObject method. I have it in my aspx page like this:
>

>scmal.StateCentralClass scMal = new scmal.StateCentralClass();
>while (System.Runtime.InteropServices.Marshal.ReleaseComObject( scMal ) > 0) {}
>

>
>in order to reduce the reference count to zero. I am going to experiment with it in my page and see if it makes my VFP objects "go away" any faster than just doing
>

>scmal.StateCentralClass scMal = new scmal.StateCentralClass();
>scMal = null;
>

>
>
>
>Maybe Ed Ruah or Rick Strahl will smell this thread and lend their $.02 as well....