>Thanks for clearing the concept.
>
>Can you give me more idea about the error ?

The specifics of the C0000005 error that is solvable with DCOM, and how to detect the condition and shut down before starting up a form in an app are written up in some detail in the FAQ here on UT.

As far as what exactly is causing your problem, I don't know. A C0000005 in general is an error caused by referencing memory that isn't assigned to the current process; there are lots of things that can cause that error to occur. It is not something that VFP traps, but a condition that, when detected by the operting system, forces the current application to terminate rather abruptly; this is an effort by the operating system to prevent an error in one process from crashing out the whole machine.

The error at termination addressed by installing DCOM still exists; we've found a workaround for it at best, No one has yet isolated the exact component at fault for causing the error, and ultimately, Microsoft will need to address the root cause within VFP 6. For now, we have a way to prevent it from occurring, and a method to detect that the error can/will occur.

If you really need to pursue it in detail, you'll have a good deal of detective work to do. The first step will be to isolate the conditions that cause there error to occur on a consistent basis - these are not just the circumstances of the VFP code itself that fails, but also the operating environments where the error occurs. Equally important is finding conditions where it doesn't occur; without doing that, you have no chance of isolating the problem in detail and fixing it - all you can do is report in detail and let Microsoft's people try to find the cause and correct it. That may be a long way down the road.