Not sure what I did or what's changed, but a previously OK app is now giving me headaches:
During the course of running an app under Access (running within Access, not as a standalone), I get an Access Error message that says I'm out of memory, and to close some open programs and try again. My actual memory usage isn't really maxed out - according to a memory monitor I have running concurrently, I range from 60M (23%) free with Acess alone running to 37M (14%) free with Access running my app. And I see no change or "spike" when the error message pops up - the graph stays pretty much flat at 14% throughout no matter what my app is doing.
I'm guessing its not actually the total memory usage its looking at since there's still free RAM left, but some portion that Access has reserved for itself which is "full". So whats really goin on here? How do I fix and\or prevent the problem? Or rather, where do I start looking to find the *real* problem, since this is really just a symptom?
For reference: I don't think I have any extraneous variables being created as I have Option Explicit statements in every module, and I don't think I'm using any variant data types. None of my back-end data manipulation is that complex or involves that much data. So where's all this memory goin to?
Thanks in advance
During the course of running an app under Access (running within Access, not as a standalone), I get an Access Error message that says I'm out of memory, and to close some open programs and try again. My actual memory usage isn't really maxed out - according to a memory monitor I have running concurrently, I range from 60M (23%) free with Acess alone running to 37M (14%) free with Access running my app. And I see no change or "spike" when the error message pops up - the graph stays pretty much flat at 14% throughout no matter what my app is doing.
I'm guessing its not actually the total memory usage its looking at since there's still free RAM left, but some portion that Access has reserved for itself which is "full". So whats really goin on here? How do I fix and\or prevent the problem? Or rather, where do I start looking to find the *real* problem, since this is really just a symptom?
For reference: I don't think I have any extraneous variables being created as I have Option Explicit statements in every module, and I don't think I'm using any variant data types. None of my back-end data manipulation is that complex or involves that much data. So where's all this memory goin to?
Thanks in advance