OK, several possible limits.
First, unless your disk has 0 free space, the odds are it isn't disk space. And a Windows folder has size limits of "available free space." Unless you have actually filled the disk, a folder cannot get too large.
Second, Access does have some internal limits. The absolute max for an Access monolithic project is 2 Gb. If your file is approaching that size, you could indeed be running afoul of the Access internal addressing limits.
Third, you can have up to 1000 modules (including any class modules associated with forms and/or reports).
The next couple of limits were harder to find.
I'm asking this for curiosity's sake. Is there a code module size limit? I looked at Access Specifications in help and didn't notice a code limit size. For some odd reason I was under the assumption that code modules couldn't exceed 64K...probably thinking of memos.
bytes.com
Max 1,024 characters per line.
Max 6,601 lines per procedure.
Max 65,545 lines per module.
To be honest, I doubt you would run into the max characters/line or lines/procedure limits. But in theory, you could concatenate something in a way to blow the chr/line limit. Just highly unlikely.
But then, there is the issue of the actual meaning of "Out of memory." This gets trickier because that is a RUN-TIME error, which means it could be something you did when the code was actually running but that wouldn't occur if no code is running.
If you know the meaning of "recursion" I can tell you that a few levels of recursion, particularly "runaway recursion," will very quickly blow memory away.
If you try to dynamically ReDim an array to very large size, that will do it.
If you try to open or create a large number of dynamic objects including application objects, that has a good shot at scarfing down memory.
If you are opening a lot of files but you are not closing them immediately when done, each open file reserves a chunk of memory for disk buffers and a file-handle structure (an internal Windows structure for file control). You could blow out memory that way. Same would be true for any recordsets. If either files or recordsets are being opened in a loop and not closed, it would be trivial to reach a point of memory exhaustion.
ocuments Folder
