Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Fatal error: Exception code=C0000005 again in VFP7

Status
Not open for further replies.

GEMINI88

IS-IT--Management
Mar 23, 2001
12
HK
I got the "Fatal error: Exception code=C0000005" error in my previous program in VPF6 with SP5. The problem never been solved even I followed some suggestions to udpate the service pack and increase the desktop memory.

Recently, I moved to VPF7 with good hope that it can fix the bugs. The error happens more frequently in Win2000 desktop after moving to VFP7. Can anyone help on this?

Many thanks.
 
Many of these errors are generated by corrupted Foxuser, Foxtask, Foxcode ... DBFs. Try to delete those files first.
You can try running vfpclean.app next.
 
Thanks Badukist. The program is running by 50 users in daytime and so the foxuser had been locked. Will try this later and hope that it works.
 
GEMINI88

Many of these errors are generated by corrupted Foxuser, Foxtask, Foxcode ... DBFs. Try to delete those files first.

In my experience badukist's suggestion is a dangerous one. Deleting Foxuser is OK since it will regenerate itself if it does not exist, but deleting FoxCode will NOT regenerate itself, and that table holds the intellisense code, the would effect disable intellisense. Start with foxuser table, and come back here if you have more problems.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
I agree with Mike Gagnon. In fact, I can't see why Foxcode should even be present in a run-time environment.

There a dozens of reasons for C5 errors -- not just corrupted tables (although corrupted Foxuser tables are a common cause). A search of the Knowledge Base will turn up a LOT of possibilities.

Mike


Mike Lewis
Edinburgh, Scotland
 
I searched from other FAQ and some of them pointed to printer driver, display card and memory. Is that true?

In my case, the error was OS dependent, it never happens in the NT4 workstation while frequently found in Win2K, infreqent in Win98 & XP. All of them are using the same exe at the server.

I believed that it should be someting crashed in vfp as when the error found in one machine, it happened to all followed. The error happened continously if I don't reindex the tables.

**still can't find a slot to rebuild the foxuser table.
Thanks all for comments.

Gemini
 
Gemini,

I've had this same problem only after converting from VFP 7 to VFP 8
...during REFRESH events, with the greatest number of Exception Crashes occurring in the Win2000 OS (vs XP home and pro). I never got the SPacks for that Win2000 OS, though.

My problem was not resolved at all by deleting foxuser, nor by deleting/reducing compound indexes (.cdx files) and re-indexing them.

The (HP) printer driver suggestions in the knowledge base helped none, too.

I speculate there is a problem with sudden form.REFRESH changes ocurring on heavily conjested parent data + multi-teired child tables.

My workaround at present has only slowed these crashes to about 20-50%:
I've reduced functions that call on my complex form.refresh procedures.

(Please let me know if you come up with a solution or work-around)



Philip M. Traynor, DPM
 
Philip, thanks for the sharing. The service pack of win2K does not help as we already got the lastest version.

I agreed with you that the error happens at the most busy time, when many tables had been opened. It comes more freqently when there is a parent & child relationship.

Quite disappointed to know that VFP8 got the same problems.

Gemini
 
I've got a lot of C00005 errors even in an clent-server aplications. The solution was to validate/pack the DBC (the next step was that I made it read-only. No errors so far).
 
You made the DBC readonly? Hmmmm interesting, I'm gonna have to think about that one.

Slighthaze = NULL

[ul][li]FAQ184-2483
An excellent guide to getting a fast and accurate response to your questions in this forum.[/li][/ul]
 
Badukist,

Can we make the dbc readonly? I tried and cannot start the program. Error message : memofile xxx.dct is missing or is invalid
 
GEMINI88

In my experience, making a DBC (or its index) read-only will cause problems, since at least the index files gets written to every once in a while.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
As I said, it is about a client-server application, database contain only connections and remote views. I've included the DBC, DCT and DCX in executable as "other files" not as "database". Everything is ok, till now (4 months). I've SET RESOURCE OFF and I have no C0005 errors any more.

 
Hi,
I encounter the C000005 error when running a form in debug/trace mode. Whilst when running the form 'normaly' no C000005 at all.Any suggestions how to overcome this?

Koen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top