>>I've read the previous threads on Fatal Error C0000005(may have missed a couple of 0's). They seemed to revolve around eliminating SCREEN=OFF in config.fpw and having IE 4.0 installed as a remedy. Having neither condition to begin with, here is the scenario which generated the problem. This only occurs in VFP 6.0, not in VFP 5.0 (Scary as it may seem)
>>
>>A view is executed, within a page of a pageframe where one of the table joins is a left outer join as only a small number of records will contain a valid reference to this lookup table. If a .null. is returned, space(2) is inserted in the field displayed. When the query executes, if the data set encounters a null on this field (based upon a foreign index integer id of 0 in the field), the fatal error is generated and VFP has to shut down. If a non-null value is located, the information displays correctly.
>>
>>No MS reported bug exists for this or the earlier fatal error problem. Anyone have some insight. Our current workaround is to create a dummy value in the table for the 0 id so we always find a value. However, we are not particularly fond of kludges.
>>
>>TIA,
>
>
>One of the solutions to eliminate C0000005 on Win95 is to install DCOM95.

Where is DCOM95 and what if anything can you do if your OS is WIN98?