VFP 8.0 - Not enough memory to complete this operation

[kenndot]

After getting one of those lovely fatal exception c0000005 errors, I got a series of error reports and sent them each time I got the message. Then, VFP 8.0 is closed automatically.

I am now not able to even open VFP 8.0. I can open vfp6.0 and can run apps that are in 6 and/or 8 just fine, I just can't open version 8 so I can't try to rebuild prgs like some of the other posts pertaining to this message say to do. The message comes up before the splash screen goes away.

I've tried:
rebooting - several times
clearing out all my temp files
looking on microsoft.com

I run on 256K, but we tried using a thumb drive with extra memory to see if we could at least get it open with that, that didn't make a difference.

Any ideas?

 

[DSummZZZ]

Try deleting your FOXUSER.* files too.


-Dave S.-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[kenndot]

tried that, any other ideas?

 

[Mike Gagnon]

Kenndot.

I got a similar message yesterday on one of our systems and if you can step through the code to where the error is generated, you may find a corrupted index on one of you tables.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[kenndot]

Hi Mike,

Problem is, I can't even OPEN foxpro anymore. The error is generated while opening foxpro, not opening or running an app, so there is no code to walk through.

 

[kenndot]

in case anyone gets this error....

start foxpro with -A command-line switch.

 

[mkrausnick]

Going back to Dave Summers' suggestion: Look for and delete FOXUSER files in all directories on your system (application directories, develoment work directories, your network 'home' directory, etc), ESPECIALLY if you have more than one version of VFP installed. Maybe also delete occurances of CONFIG.FPW, although I've not heard of that file causing problems before. As a last resort, remove and re-install VFP8.

Mike Krausnick
Dublin, California

 

[gwan]

i got similar problem with vfp7.0 in my old computer (celeron 700) then i try to update mainboard driver, thats solve my problem

 

[badukist]

Try deleting other files opened at startup (foxcode,foxtask), try to rename TaskPane folder, maybe is a corrupted DBF there.

 

[Mike Gagnon]

badukist

Try deleting other files opened at startup (foxcode,foxtask)

I would not recommend to delete the foxcode table. That is the table that holds the information for Intellisense.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[kenndot]

Starting foxpro with a command line switch fixes the problem and that way the most you have to do is reconfigure you tools/options settings, which I didn't end up having to do. It's a whole lot easier than tracking down and deleting all your foxuser files and what not.

Although before I tried the command line switch, I HAD in fact tried to delete all those files and it didn't work anyway.

 

[kenndot]

I didn't quite finish before I hit submit... Here's the actual steps I took.

Added -A to the end of the target path of the foxpro icon
started foxpro - just to make sure it works
close foxpro
remove the -A you added from the target path
started foxpro

very simple, no deleting of files were necessary