Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Access Denied C0000005 error in VFP5
Message
From
28/12/1998 21:33:32
 
 
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00171005
Message ID:
00171019
Views:
63
>>VFP5.0a - SP3,
>>WinNT4 - SP1.
>>
>>I'm having trouble with a c0000005 (access violation) error when I close my EXE. I've traced it to grids on a few forms - if those grids are in focus the EXE will crash when the EXE closes, not when the form closes. The Dr.Watson log says it is a DllOleInit function error.
>>
>>If I run on Win95 I usually (not always) get a GPF under the same circumstances.
>>
>>Any ideas thankfully accepted
>
>Bring NT to SP3 or SP4, which add the DCOM components, as will adding IE 3.02 or later.
>
>On Win95 boxes, add DCOM via DCOM95 from the MS site, DCOM98 from the VS distribution, or add IE 3.02 or later.

My apologies - I stopped reading at C0000005!

I'd still apply at least SP3 to NT; there's a tremendous amount of stuff fixed in it, and even more in SP4 if it doesn't bite you during the installation...

If you're using many .DLL DECLARES, I've avoided some problems releasing .DLLs by invoking the ExitProcess() API call rather than using QUIT. Try:

DECLARE ExitProcess IN WIN32API INTEGER uExitCode
=ExitProcess(0)

in place of QUIT. I don't know exactly why this works, but it fixed some problems I had after far too many DECLARE...DLLs and DLL call invocations.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform