- #EXCEL NOT ENOUGH MEMORY MAY NOT COMPLETE THIS OPERATION HOW TO#
- #EXCEL NOT ENOUGH MEMORY MAY NOT COMPLETE THIS OPERATION UPDATE#
#EXCEL NOT ENOUGH MEMORY MAY NOT COMPLETE THIS OPERATION UPDATE#
Having tripped across this old post of mine, and seeing it's had a fair bit of interest, I thought maybe an update would be in order? I have not lost an object to code corruption in over 5 years, and that was back in the day when I was still using A97. I program daily in Access, working with non-trivial apps that use lots of code, including plenty of standalone class modules. This is superior to simply importing from your existing corrupted front end because the import can import corrupt structures that won't survive a SaveAsText/LoadFromText cycle.
#EXCEL NOT ENOUGH MEMORY MAY NOT COMPLETE THIS OPERATION HOW TO#
In regard to how to rebuild the project, I think I'd go the drastic route of exporting all the objects with Application.SaveAsText and importing them into a new blank database with Application.LoadFromText. It will do nothing to recover an already corrupted project. These practices insure that the code in a non-corrupt project stays in as clean a condition as possible.
This will clean out any crud that accumulates during regular development. Periodically decompile your project and compact and recompile it. I probably compile my project 100 or more times a day when coding. You'll quickly find out where you have invalid code and you'll need to fix it.įrom now on, when programming, compile frequently, after every two or three lines of code. Having set up your environment, go through all the modules in your newly recovered project and add OPTION EXPLICIT to the top of every module that lacks it. The point here is to make debugging and compiling as easy as possible. I also recommend adding the CALL STACK button (from the VIEW menu), as it's handy for debugging errors in break mode.
In the VBE, customize your toolbar so that the COMPILE button is easily accessible (it's on the Debug menu). In VBE options, turn on REQUIRE VARIABLE DECLARATION. In VBE options, turn off COMPILE ON DEMAND (see Michael Kaplan's article on DECOMPILE for details of why).
You need to rebuild it from scratch and then use proper Access coding practices: The VBA project in your front end is likely corrupted.
0 kommentar(er)
