Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Oops: any Debugging gives C00000005 error!
Message
From
22/08/2000 11:55:57
 
 
To
22/08/2000 11:45:19
Hermann Strijewski
Fast Track Business Solutions
Toronto, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Object Oriented Programming
Miscellaneous
Thread ID:
00407781
Message ID:
00407790
Views:
22
>I have written a fairly large application using (regrettably) the VFP6 Foundation Classes Framework.
>
>I have been fighting this C0000005 error that occurred frequently throughout the app, mainly by simplifying things, removing things etc.
>
>Now I have this strange situation:
>
>0. If I don't bring up the Debugger, the app runs ok, and exits cleanly.
>1. If I'm in the app and no window is open, I can bring up the Debugger ok from a menu option.
>2. With the debugger open, as soon as I do anything, click on any toolbar button or select a menu choice to launch a form, it gives C0000005
>3. If anywhere from within a form I launch the Debugger, it immediately gives C0000005
>

This is often a problem caused by an invalid value carried in the FOXUSER file for one or more debugger settings; try renaming the FOXUSER file and see if the problem goes away, if it does, and you need things other than the debugger settings, you can try deleting out the records related to the debug settings and packing it to eliminate the references causing the problem.

>Can anyone give me some pointers as to where to look for this, or what would cause this.
>
>I don't want to go back to 2 months earlier code, which was last when I did not have this error.
>
>Thanks so much in advance for any advice.
>
>Hermann Strijewski,
>Clearwater, FL.
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
Reply
Map
View

Click here to load this message in the networking platform