Dear Jeff:
If you're developing and need to test this, I would try adding more memory
to the system and see if the problem "goes away".
If it does, then you could watch the available system memroy. It may be
trending down and down as you click these combo boxes. That would be a good
diagnostic.
You can also watch the system memory without adding more memory. But there
may be little memory available when you start the test, and the trend would
be harder to catch. Also, if you're that close, you may not be able to open
the utility to observe this.
Instead of installing more memory, you may be able to cut back on background
tasks. Task Manager will show you that, as well as the memory usage for
Access. It updates frequently as well. Some of the applications that may
be running may not be readily identifyable from the Image Name shown there.
We may need to find you a reference, probably on the net. Don't just shut
down any old thing! It's saver to temporarily disable application, removing
it from startup for example, than to just start killing tasks. You will
likely kill something essential, and it's reboot time!
If it running out of memory, then it may be something in your code that you
need to fix. Deallocating an object you have declared and instantiated is
one important issue here. Use:
MyObject = nothing
after closing the object.
There have been bugs in Access that leak memory, too. You may want to look
those up and try to see if you can identify where you have used facilities
with this problem. This includes my nemesis, a leak in MDAC. Heck, now I
need to go see if it has been fixed. In my application, scrolling through
records on a form causes a blow-out, but only after 313 clicks of Next. No
user has ever found it, but I know it's there. Like waiting for the other
shoe to drop.
Tom Ellison
