Microsoft visual foxpro серьезная ошибка код исключения c0000005

Answers

• C00000005 is not a VFP error but a Windows OS error and it can be issued for many reasons.

  People have there own pet reasons as to why it happens.

  Normally, it is due to an error in the program creating a condition that the OS cannot recover from.

  I have found that the specific Release of objects by issuing the command

  Release obj1, obj2, etc.

  certainly helps to reduce these errors. So if you have issued the command CreateObject() then you certainly need to specifically release those objects.

  Also, if you have invoked external procedures contained in DLLs and APPs, you need to do the specified Close routines in order that the DLL/APP can release its own objects.

  If you do a search on the web site and of the web in general for C00000005, you will get a lot more suggestions as to the cause.

  ---

  The English Bob

  • Marked as answer by

    Wednesday, September 24, 2014 9:58 AM

• There is a known bug in VFP 9 SP2 involving forms with grids called from menu items. Go to this page: http://fox.wikis.com/wc.dll?Wiki~VFP9SP2BugList~Wiki and search for «grid» and see whether it applies here.

  Tamar

  • Marked as answer by
    Carl Cai
    Wednesday, September 24, 2014 9:58 AM

• One more possible cause:

  Does your code use  RESOURCE  file?

  You have to check SYS(2005)  and SET(«RESOURCE») to answer it.

  If the resource file is used the you should delete all its records. If this does not help or if the resource file is not used then the answer from English Bob could help and then you may continue to Tamar’s hint.

  If nothing helps then compile the app with debug info which could provide better picture about the problematic line of code. BUT it is hard to identify the real problem in this kind of errors and you have to play with your code …

  • Marked as answer by
    Carl Cai
    Wednesday, September 24, 2014 9:58 AM

Answers

• This error generally occurs on the systems where you do not have complete VFP installed and when ever some error occurs it gives such kind of error. Just try and replicate the senarios where the error is coming on the system where VFP is installed and look for the error which may be conditional.

  Hope this will solve your problem.

• If you can come up with a reproducible scenario (one where you can say:»do this, do this and then this and then you will get a C000005 errror» and have it occur every time, on every machine ) Then someone might be able to help.

  Without it, there is nothing anyone can tell you (as you have been told before) because the nature of these errors is that they are not specific to the application, the code, or the development tool.

  >>If it cannot be minimized, what will be the reason for us to continue the development of FoxPro… ?!

  But if it is a windows/hardware conflict on the customer’s machines then it won’t matter whether the development is in FoxPro, VB, ASP .NET or anything else — the problem will remain!

  The normal reaction of people in this scenario is to blame the application. But you cannot fix what isn’t broken and you need a reproducible scenario that will work in order to identify the problem. The hardest thing in the world is to convince Network people that the problem is there’s not the application’s.

• C5 is not a FoxPro error. It is a Windows error and there is nothing Fox can do to control/prevent/trap/avoid it. Basically it means «memory is corrupt and I can’t recover». Because memory is corrupt, you can lose data. The best you can do it try to track down what’s causing the memory issue. You could decide to move away from Fox to something else, but c5 errors can happen an ANY application.

Answers

• This error generally occurs on the systems where you do not have complete VFP installed and when ever some error occurs it gives such kind of error. Just try and replicate the senarios where the error is coming on the system where VFP is installed and look for the error which may be conditional.

  Hope this will solve your problem.

• If you can come up with a reproducible scenario (one where you can say:»do this, do this and then this and then you will get a C000005 errror» and have it occur every time, on every machine ) Then someone might be able to help.

  Without it, there is nothing anyone can tell you (as you have been told before) because the nature of these errors is that they are not specific to the application, the code, or the development tool.

  >>If it cannot be minimized, what will be the reason for us to continue the development of FoxPro… ?!

  But if it is a windows/hardware conflict on the customer’s machines then it won’t matter whether the development is in FoxPro, VB, ASP .NET or anything else — the problem will remain!

  The normal reaction of people in this scenario is to blame the application. But you cannot fix what isn’t broken and you need a reproducible scenario that will work in order to identify the problem. The hardest thing in the world is to convince Network people that the problem is there’s not the application’s.

• C5 is not a FoxPro error. It is a Windows error and there is nothing Fox can do to control/prevent/trap/avoid it. Basically it means «memory is corrupt and I can’t recover». Because memory is corrupt, you can lose data. The best you can do it try to track down what’s causing the memory issue. You could decide to move away from Fox to something else, but c5 errors can happen an ANY application.

Answers

• Hi

  I now have the answer which came from Christof Wollenhaupt on the UT thread.

  Delete anything in C:Documents and SettingsusernameApplication DataMicrosoftVisual FoxPro 9.

  And then Fox runs as if nothing was ever wrong!

  Thanks for all your help

  Mike

Answers

• Hi

  I now have the answer which came from Christof Wollenhaupt on the UT thread.

  Delete anything in C:Documents and SettingsusernameApplication DataMicrosoftVisual FoxPro 9.

  And then Fox runs as if nothing was ever wrong!

  Thanks for all your help

  Mike

Contact US