Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The VBA project in your front end is likely corrupted. You need to rebuild it from scratch and then use proper Access coding practices:</p> <ol> <li><p>in VBE options, turn off COMPILE ON DEMAND (see <a href="http://trigeminal.com/usenet/usenet004.asp?1033" rel="noreferrer">Michael Kaplan's article on DECOMPILE</a> for details of why).</p></li> <li><p>in VBE options, turn on REQUIRE VARIABLE DECLARATION.</p></li> <li><p>in the VBE, customize your toolbar so that the COMPILE button is easily accessible (it's on the Debug menu). I also recommend adding the CALL STACK button (from the VIEW menu), as it's handy for debugging errors in break mode. The point here is to make debugging and compiling as easy as possible.</p></li> <li><p>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. Then compile. You'll quickly find out where you have invalid code and you'll need to fix it.</p></li> <li><p>from now on, when programming, compile frequently, after every two or three lines of code. I probably compile my project 100 or more times a day when coding.</p></li> <li><p>periodically decompile your project and compact and recompile it. This will clean out any crud that accumulates during regular development.</p></li> </ol> <p>These practices insure that the code in a non-corrupt project stays in as clean a condition as possible. It will do nothing to recover an already corrupted project.</p> <p>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. 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.</p> <p>I program daily in Access, working with non-trivial apps that use lots of code, including plenty of standalone class modules. 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.</p>
    singulars
    1. This table or related slice is empty.
    1. POMS Access: There isn't enough memory to perform this operation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid-W-Fenton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks David. Re 1, what does that do? (not covered in Michael Kaplan's article) 2: always on. 3: I always compile after every code change. 4: always use this. 5: I also compile a lot. 6: I also regularly decompile/recompile. I too work daily with Access, for ~10 years. Haven't lost any code - I too have a lot of VBA modules/classes - but occasionally get a corrupted form or report. But recently I've been getting this 'memory' error. Today I lost most forms, and all reports! Fortunately, I had text backups of all objects from yesterday, and used LoadFromText to recover forms and reports.
      singulars
      1. PO
      1. USmaxhugen
    2. COThe article explains why you don't want incremental compiles, because they increase the number of compilation levels that VBA has to keep track of. Explicit compiling is a complete compile. You might want to check the Help file article on COMPILE ON DEMAND (hit F1 while viewing the OPTION | GENERAL tab).
      singulars
      1. PO
      1. USDavid-W-Fenton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload