I was only mentioning the fact that DCOM was present so that I didn't get another reply suggesting that I install DCOM. This is the PAT answer. I didn't realize you were the defacto 0xC0000005 error whipping boy.

It would be nice to develop in WinNT, however I don't have that luxury since most people who buy my software use Win95 and Win98. Yes, Fox executables do not run the same when developed and compiled on NT and used on Win9x platforms. Form sizes change and support for character sets other than the english alphabet. Thai font support is different from NT to 9x, for example. The rest of the world is not as computer literate as they might be in a country like the US. They don't want to deal with NT. WinNT has many other problems related to video cards and certain CPU's as well. Besides, that's not a good answer anyway.

There is no need for YOU to apologize for anything. When I worked in high tech manufacturing in the US, we had a thing called an extended testing environment BEFORE releasing any product. Imagine selling disk drives to your most valuble customers with a note saying "Please report the bugs and flaws and all the conditions surrounding the problem, because we didn't have time to do it" You would never sell a single disk drive unless you were the only disk drive maker.
If I had not installed Visual C++ there would be absolutely no information to report. Memory is slam dunked immediately upon execution when run outside the VFP environment. When I try to debug using the Fox debugger, it doesn't have the error. There is information in the C++ debugger suggesting there is a problem with VFP6R.dll. If no person on this thread has seen this, I will be more than happy to report the conditions to MS. However UT is always my first recourse after having lost X amount of money chasing down an error that should have never happened in the first place.

Eric K.

>>Well, DCOM is activated in Win98 according to the registry. The explanation in the C++ debugger is this.
>>
>>Unhandled exception in .exe(VFP6R.dll) Access violation.
>>
>>Line in callstack:
>>VFP6R! 0c0989a4()
>>
>>Disassembly:
>>0C0989A4 mov byte ptr [edi+7EF0FFFFh],cl
>>
>>Quick Watch:
>>CXX0013: Error: missing operator
>>
>>I find it hard to believe MS did not no about this prior to releasing version6.
>>
>>BTW, this does not occur when run as .app. So, what's new?
>>
>
>Apparently, no one is reading what I've posted - they stop reading when they see C0000005 FIX. The DCOM fix addresses one very narrow set of circumstances that cause a C0000005 error in the runtime environment where you are running an application that starts without the main VFP window visible (SCREEN=OFF in CONFIG.FPW, or similar), and then the VFP main window or a top-level form is made visible subsequently. If DCOM support has not been installed, at shutdown, the runtime program will terminate with a C000005 error. Installing DCOM support prevents that error from occuring.
>
>There is no (0, nada, nil, none whatsoever) evidence that DCOM support is responsible for, or should be considered as a fix for, C0000005 errors in general. The error is an operating system level error indicating that there has been an address space access violation; lots of things can cause this. We've isolated one instance that plagued a number of people early on, and found a workaround for that case. Under no circumstance have you been lead to believe that DCOM is a universal fix for errors of this class. Careful analysis of the circumstances surrounding a repeatable error, especially when environmental considerations affect the repeatability of the error, is needed to come up with fixes for the problem. If you have a repeatable error, document the conditions of contest here and submit a bug report to the people at MS. We as developers don't have the source code to VFP6, can't write a service pack to fix it. If you document the conditions that cause it, we can try
>other environments to see if the error reproduces there, and if not, we may be able to suggest things as a workaround or a method to predict and avoid there error. You've provided none of the needed information, just I got another C0000005 error that DCOM doesn't fix. To me, that isn't terribly helpful.
>
>The best fix I've found to date for debug and design time errors is to develop on WinNT. There are a number of things that have been reported as causing intermittent, or even consistantly repeatable, errors in the design and debug modes, that simply don't happen developing on a box running NT 4.0 with SP3 or SP4 and IE installed, with VS6 SP1 applied.
>
>Sorry for this screed, but I'm tired of apologizing that the DCOM fix we've documented doesn't fix all known problems in all known environments where VFP6 is concerned...