>Hey George,
>
>I'm not sure of the problem with DCOM95, but I tried that solution on 3 WIn95 machines and afterwards 2 of the 3 generated GPF's before the VFP program started, so it was worse than without DCOM. Someone told me they used DCOM98 (even on 95 machines) and it worked, so I'll try that out. But I don't think I'd recommend DCOM95! I didn't try to debug DCOM95, so that might be fixable, but I was tired of working with this error.

Hi Randy,

Thanks for the info. I don't know if the following is related to the problem whatsoever. I think it's worth repeating, however, within the context of the error that occurred.

Ever since I got this new machine with Win98 on it, my G: drive, which I generally reserve for temporarily attaching and detaching from our various servers, has been automatically mapped to the local server. When I say "automatically" I don't mean during startup. I mean that every two hours, something decides to map the drive without any external intervention.

In the course, of tracking this down (I'm still working on the problem), I created a small prg class to go out once a minute (using a timer), and check to see if the drive was mapped. In order to determine how often this was occurring, the class had a custom property to hold the value, and the Timer event would increment it every time it fired. For some reason (my own stupidity most likely), rather than referencing properly within the timer event as: This.Parent.nCounter = This.Parent.nCounter + 1, I wrote: This.nCounter = This.nCounter + 1. Well, the first time the timer fired, I got the same Fatal Exception error message and number, and VFP 6.0 closed down.

I'm wondering if something similar (an unresolvable reference) isn't causing this problem.