Search results

There are lots of subs and functions. I do not consider subs with more than 40 lines as "long code". There are longer subs, with 150 or more lines. I don't think this will influence the compiler. Or would it? The project is very old. Subs and functions are refactored/reorganized when they are...

Two different computers, and a virtual machine, all give the same problems with this project.

The Problem occurs on two different Systems, different OS, and different Access Version. I even tried an Import on Access 2019. No Luck.

Little steps did not solve the problem. At first it looked like everything was ok, but other unpredictable messages occur, until I was back at the known Problem.... I will probably have another go at single Import through LoadFromText....

Will changing the order of references shed any light on the problem? I think that loading of referenced libraries are failing is a result of the first problem, where Access has a problem with its memory. I played around with process explorer, vmmap, procdump and winDbg.... None of them give any...

Before the problems starts, there are no errors whatsoever. When the compilation fails, the message is "not enough memory" or Access shows a message that a normal Access statement like "Left$(...) or Trim$(...)" is not valid.. That is the decompile I am using.

Is that a suggestion to use CoPilot in VBA? The sample is just a sample to illustrate the behavior.

Thanks for staying with me on this problem and think things over. I will try to answer all the questions and fill in the blanks The deleted object are not returned to the project, they are obsolete and will not be used again. So it seems that deleting some objects will provide some space for...

As stated in multiple comments, Decompile & Repair does not solve the problem. Unless you mean something else with decompile/recompile.

Nice testing... The total of modules, including forms and reports which have modules, does not exceed 800. I did the same kind of testing with forms, subs and functions in the past. I did not continue in that direction cause the numbers did not match to the actual project. Another test is still...

Right, when the problem occurs, simply opening the project, compiling is not possible until some other object (form or reports) is deleted. The Syntax of the deleted forms and the new code is/was correct. The project compiled without the new code and compiles without the old form. The number of...

Thanks, I will keep that in mind and as a last resort try to eliminate vbWatchdog. I searched the internet for this problem and never found any relation to vbWartchdog. I would presume that more people would have complained about this add-in.

What does that mean, "some number of modules"? There are lots of modules and classes in this project, together they definitely have more than 64K characters in then. Are there limits to some types of modules?

Name Autocorrect was never enabled in this project

No module exceeds the size limit. If this problem occurs, even the adding of a new form with only an onLoad method will fail the compilation.

Add-in vbWatchdog is installed. Import tried through saveastext/loadastext and direct Access import....

No timers active, no open forms. When this problem occurs, I close the project and restart Access in decompile mode, Then Compact & Repair the accdb file. Then I restart Access, open the database and try to compile after I delete one or more older forms, until the compilation is successful...

Bizarre it is... I use two different development Systems, one still at Win 7 the other at Win 11, both have the save problem with this accdb project. Other projects run fine. New development in this accdb does not give any issues when several Forms have been deleted. Eventually the problem...

Thanks for the quick response. The Message "not enough memory" does not apply to the computer itself. The problem exists on win7, win10 and win11. Today, with 32 GB memory and enough free space on disk. Compacted, the size of the accdb file is 55 MB. Recursion is not a problem, the code runs...

As the Title suggests, I am experiencing strange things in the VBA Editor of Access 2007. I am looking for an explanation and of course a solution to the problems. Example 1 If I type something like this, in code that would normally compile just fine Dim aString As String After enter, it...