Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Low System Resources

Status
Not open for further replies.

jlitondo

MIS
Jun 27, 2000
175
US
Yet again.when I try to go into the code window of some forms, I get the error message above.At this point,my resource meter indicates that I'm down to about 12% free resources (how can that be?). Before going into the code window however, sys resources are up at 88%.I'd expect these resources to be freed up as soon as I close the code window but the % level stays the same.
I browsed the forums here for a possible explanation of this error and have tried several things but have not been able to resolve this problem. I checked my forms to ensure that I do not have them loaded with excess controls and vba code then opened up a new blank database and imported all the forms from the previous database and checked the references that I needed.I was then able to go into the code window of the new mdb without system resources going below 77% and make edits.But when I try to run some forms, I get an "Operation not supported within transaction" error.I initially thought that this may have something to do with my new database being locked somehow but could not see how this could happen since at the moment I'm the exclusive user.
Finally when I close and open the db, all of my macros, reports, modules and half of my forms wind up missing !!! forcing me to reimport them.
What is causing this problem? Is system resources directly related to RAM or is it another name for it.I'm running Access 2000 on Win98 with 96megs of RAM.I also checked the Kb on Microsoft's site but it has very limited information on this type of problem. [sig][/sig]
 
if this only occurs while developing your application, my best guess is that your code is flawed, and is creating a memory leak somewhere, make sure you free up variables, and try not to get into a loop of creating new data types without freeing them, just cuz you close your software, doesnt mean that it wont remove the junk floating around in the memory automatically.

that's my best bet. [sig]<p>Karl<br><a href=mailto:kb244@kb244.com>kb244@kb244.com</a><br><a href= </a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>
[/sig]
 
So far this only happens as soon as I open up the code window.Shouldn't this window free memory once it's closed?
 
jlitondo,

Sounds like you're having fun.... <smile>

Two suggestions....

1) Have you tried importing one form/other object at a time?

2) Have you asked your question in the Access forum? (it *is* Access isn't it?) [sig]<p>Mike<br><a href=mailto:michael.j.lacey@ntlworld.com>michael.j.lacey@ntlworld.com</a><br><a href= Cargill's Corporate Web Site</a><br>Making mistakes, so you don't have to. &lt;grin&gt;[/sig]
 
Fun, aye? The Kb acknowledges this error message as a bug in Access and recommends downloading the Microsoft Office 2000 SR-1/SR-1a patch that's supposed to but didn't fix the problem.However, I made an intersting discovery.After opening up the code window for a form and clicking on the restore window button, I noticed that the code windows for all of my forms were open as well.I minimized the one I needed, closed the rest saved it, closed it and opened it up again and taraaam! The resource meter stayed at the same percentage.So far I have been able to open, modify and close code windows without resources going low.
It seems to me that this may have been all/part(mostly) of the problem.All the open code windows,even though unrequested at that instance, were hoging up memory.One thing though is that on closing and reopening the mdb, the code window goes back to having ALL the database's code windows open and I had to go into the codewindow of one form again and close all but one code window.Perhaps their is a setting that can permanenty save that setting but I don't know how. So far so good but if anyone has a better cure to this problem please let us know. [sig][/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top