I've been bitten by this error too, but I encounter them most often in the development environment. Yesterday I got a C0...5 error just by double clicking on the BeforeOpenTable() entry in the property sheet for a report.

>To be honest, I've been a bit distressed about seeing all the posts about this error. Personally, I'd only encountered it twice (before this evening). Once was with an SDI application where the computer didn't have the DCOM95 program loaded. The other was when I did something very stupid with an ActiveX control. Well, tonight I've encountered it several times, and I think I *may* have figured something out.
>
>Before I go further, I should point out that this is all conjecture on my part. It's simply based on my experience. It may or may not apply to some of the other instances of this error, and it may or may not be the solution.
>
>I've been working on a personal project that uses the ImageList and TreeView ActiveX controls. One of the objectives of this is to be able to have it work in both VFP 5.0 and 6.0. Since the controls that come with these two products are different, I thought that I'd subclass both.
>
>The TreeView subclasses well. I was able to create a prg and it worked just fine. The ImageList does not. Using the same technique, I kept gettting syntax errors followed by the C0000005 error. Once I did a regular AddObject(), and set the properties externally, everything was fine.
>
>Apparently (and please take this with a very large grain of salt, or in other words, be cautious), if the control has a visual presence, you can subclass it to your heart's content. If it doesn't...well, be prepared for the C0000005 error.