>It's nice to see how we can discuss the C00005 error in relation to DCOM95 again and again. Maybe we can concentrate on my original question again. My C00005 error is not related to DCOM95. I installed DCOM a few times now (VS6.0, IE4.0 and just download v1.3 from the Microsoft-site) but it doesn't solve my problem.
>
>Does anyone has other ideas?

There are any number of things that can cause a C5 error to occur - it's an indication that something internal to VFP made an invalid memory reference, and an operating system level error occurred, forcing VFP to shut down in an abnormal fashion. In addition to several things like DCOM or invalid entries left in the FOXUSER file affecting debug sessions and the infamous HP driver problems, there are lots of things that can and do cause problems.

There is not, nor will there ever be, a complete, single solution to all occurances of the C5 error, any more than there was a single cure for the infamous GPF. The error occurs as a result of any number of things, and no single solution is available to address them all.

The best that can be hoped for is that Microsoft will track down and correct problems internal to VFP6 that can cause the error in upcoming service packs or future releases.

>Marco