>>>>>
>>>>>
>>>>>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?
>>>
>>>
>>>You can download it from Microsoft.com, but it is for Win95 only. Win98 should be ready to go.
>>
>>
>>I have been getting this error fairly often as well. I am running WIN/98 and DCOM was installed during the Visual Studio install (as well as IE 4 SP1).
>>
>>I have just installed on a brand new machine so the environment is still fairly clean.
>
>So that everyone will know the current state of this, dcom98 was installed on this machine and the error is still occurring. What we have done to work around it is to not allow a null value or "0" id to be returned in the query. If a null would otherwise be delivered in the view, we hardcode a record in the target table with a valid id that we deliver to the view which has blanks in its fields. Problem with this is that it is record 41 at the present time and it would require us to preset record 41 in the table. . . .well you are all aware of the followup problems. We will report this to M$ so that possibly it will be solved before 7.0 is released.

The DCOM fix is not a generic solution to all C0000005 errors; it specifically deals with the one related to "SCREEN=OFF". The C0000005 error is an operating system level trap of a memory access violation (lots of things can cause it; it does indicate a bug, but it is not fixable in a generic fashion for all possible causes of the fault. As an example, a memory access violation could occur as a result of a corrupted .DLL, .OCX or executable, and it would be unreasonable to belive that all memory access errors were correctable by loading DCOM. Then again, some people believe the hype about things like First Aid and Norton Utilities ability to trap and correct GPFs, too...)