Out of Memory Error

There is a debug error talking about running out of memory. It seems to happen when a patient is opened from the patient list and closed again about 30 times. This has been a problem since ~Jul 2010
The error is (at least in this instance):
Run-time error '2004': There isn't enough memory to perform this operation. Close unneeded programs and try the operation again.
Continue (grayed) end debug help
Clicking help just gives a gray screen.
Further troubleshooting
When does the error happen?
I can replicate the error (i.e. make it happen consistently) by opening and closing patients about 30 times. The error has also happened when adding a new patient.
- Does anyone know of another replicable way of making this error happen consistently? Knowing how to trigger this might help me eliminate the error. Ttenbergen 10:01, 5 April 2011 (CDT)
- Sorry,no.--CMarks 08:25, 11 April 2011 (CDT)
- Has this happened to anyone lately? Ttenbergen 17:02, 2012 November 7 (EST) Template:Discussione
- I get this often when I have an admit and discharge of a patient I logged with minimal data set-before I've entered APACHE....occurs right after I put in D/C date and time.[patient admitted and discharged over weekend usually]. I just hit the "END" and carry on.--Llemoine 08:05, 2015 June 29 (CDT)
- Haven't seen this in a long time.--CMarks 07:50, 2015 June 26 (CDT)
- not seenLisa Kaita 08:01, 2015 June 27 (CDT)
Details
I am able to reproduce the error if I manually open and close pts from patientlist pick button and view form door button. I wrote a test program to see if I can force the error programmatically; the program opens and closes patients 100 times, but this doesn't trigger a problem.
The error does not happen if I just open and close the patient viewer directly, i.e. not from Patientlist.
The error seems to happen upon the doCmd.Openform in sub cb_pick_click.
There was a theory that this is related to battery power vs. mains power; I replicated the error on my PC, so I really doubt it has anything to do with that.
It sounds like most people have had this error at times, and it seems to be more prevalent at high throughput locations.
When the error happens, task manager looks like the memory is not the problem, but CPU load spikes.
Restarting CCMDB.mdb "fixes" the problem, but that's not a solution.