Debugger BUG

[skuhlman]

I'm running VFP7.0 SP1 on a Windows 2000 Profesionall operating system. I've been using this computer for over a year with no problems. About a week ago, I started having the same problem consistantly occure. Whenever the debugger is started (either through SET STEP ON or suspending after an error), I can see the code, watch window, call stack... as normal, but as soon as the code resumes I get the ever helpful (NOT) C000000005 error.

I've tried changing the debugger to a foxpro frame and also changing it back to a debugger frame. no luck!

I've tried uninstalling VFP and reinstalling it. no luck!

I've tried deleting the FOXUSER files. no luck!

This problem happens at any time from the most complex code to a simple 2 line program that assigns a value to a variable and prints it out.

HELP!!! I NEED MY DEBUGGER BACK!

 

[craigber]

Did you delete the correct FoxUser files? The ones in HOME(7)?

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[rgbean]

While it may seem unconnected, are you running anything new in the background? e.g. Screen saver, anti-virus scanner, pop-up stopper, etc.

Have you run a virus check AND a ad/spy scanner (like Ad-aware or Spybot)?

Are you running anything "new" that might be taking up more available memory?

Rick

 

[skuhlman]

feeling stupid now... it looks like it WAS the FoxUser file in the VFP directory. I had been deleting the ones in my startup directories instead of the ones in the VFP directory. The problem is fixed and the debugger is working fine now.

 

[rgbean]

Yup, it's always a good idea to check the current location of the resource (FOXUSER.DBF) file with:
?SYS(2005)

Rick