Error - 43 - There is not enough memory to complete this operation


  • Error - 43 - There is not enough memory to complete this operation



    Massimo Senatore


    Delelopment visual fox pro
    Tuesday, October 04, 2011 7:26 AM


All replies

  • Hi Massimo,

    one reason for this might be a 'overloaded' menue with 40+ bars:

    If this is not the case, have a look at these links:

    And it also could be a corrupted MEMO table

    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011
    Tuesday, October 04, 2011 7:42 AM
  • Maybe you really have not enough memory... I would recommend a few more links:


    Tuesday, October 04, 2011 3:08 PM
  • thank you very much. I solved the file was corrupt vfp.exe

    Development visual fox pro
    Wednesday, October 05, 2011 3:22 PM
  • I'd like to add, also check if too many errors when compiling/building your application. Accumulated trapped errors generated eat-up your IDE memory. This happens to me when I misuse an outdated gdiplus class that links to several classes.

    If file corruption is not the case.

    Tuesday, October 11, 2011 7:09 AM
  • Try deleting .CDX files and rebuild it. This work for me.
    Sunday, March 27, 2016 12:20 AM
  • A corrupt EXE ( or runtime DLLs) may cause any error, but what did you do? Reinstall VFP? Did you keep a copy of the corrupt VFP.exe? Is there really any difference between the old EXE and the new one? You can easily see, if you compare with == as in FILETOSTR("corrupt.EXE")==FILETOSTR("working.EXE")

    If you judge a message saying "Visual Foxpro has stopped working" as message about a corrupted EXE, you should learn this message is just the new form of a C5 error. It is not talking about the EXE, but only the current process.

    Any corrupt CDX or FRX or any corrupt file processed by VFP can cause that error, you might really have insufficient memory. Even just a REINDEX can take lot of space, if you reindex a large DBF. It can consume more memory than available via SYS(3050) and even if that is far below 2GB you can get this error.

    In short again "some app has stopped working" is only addressing the in memory process of that app. It's not talking about the EXE file and not telling, that this EXE got corrupt or will never again work.

    Bye, Olaf.

    Olaf Doschke - TMN Systemberatung GmbH

    • Edited by Olaf Doschke Sunday, March 27, 2016 2:17 PM
    • Proposed as answer by yanyee Monday, March 28, 2016 8:33 AM
    Sunday, March 27, 2016 2:09 PM