>i don't think this problem is entirely related to dcom95. When I installed VFP6 from visual studio, I was required to install the dcom95 update. I still get lots of of C00000005 errors.
>
>I think this is occuring during the release of objects. I have a problem with an application that produces the error in runtime but not in development (same machine). I tracked it down to a clear all. I figured, why do I need a clear all when I exit in runtime? so I commented out the clear all when running runtime. No more errors.
>
>I also got the error at other times. When I tracked it down to the method that was running, I put explicit RELEASE statements that would release any object references. Normally, when a variable goes out of scope, the object it references is released. It seems that sometimes this automatic releasing of objects is causing the error. What is really difficult is that it won't happen with debug on (at least not all the time).
>
>My experience seems to suggest this error is created almost exclusively when objects are being released after their last reference has gone out of scope. I don't want to have to explicitly release all of my local variables but that seems to be what fixes the problem.
>
>I think it may help to explicitly define any variables used. I know I should, and I don't always do this, but it seems that by issuing LOCAL or PRIVATE before setting the variable makes a difference.

There is one particular C000005 error that the dcom fixes, that is, when IE4 has not been installed on a non-vfp6 machine. Other than that, what you're discussing sounds like a number of reported errors with the same C000005 message, I've had some myself. Maybe, what you suggest might even resolve that problem, it's worth looking at...