Memory problems with Access 2000! 1

[HIM]

I am having serious problems with an Access 2000 application I am building.<br>The application is a system to handle the execution of canoepolo turnaments with all the contraptions they produce. The thing is, that I have designed a form with several subforms where the actual execution takes place. You select a macth, and then you can with the teams playing, enter goals and penalties. The form also have a watch build in (OnTimer). Now, I am not able to execute 1 match of 2*10 minutes before I get the message that the machine is out of memory. The only place I can see that there might be a problem is the fact that I am running 2 action queries every second. DoCmd.OpenQuery(&quot;UpdateQ&quot. Now, since they are action queries, they do not produce a recordset, and therefore I have nothing to close.<br><br>Please, if there are anybody out there who have tried anything like this before, I will be grateful for some help.<br>The database is too big to describe here, but is easy to mail. (1.5Meg .Zip).<br><br>Thanks in advance

 

[Guest_imported]

We are having the same problem - once converting the database to Access 2000, the file gets enormouse (and for no apparent reason).&nbsp;&nbsp;Also, queries and such instead of taking minutes take up to an hour now!!!!<br><br>

 

[cmmrfrds]

Two questions. Did you convert your database from access 97 or is it a new access 2000 database form the start? Second, Are you using Win 95, or Win 98? What is your OS? I may have some input depending on the anwers since I had a similar problem with Memory in access 2000.

 

[HIM]

It is a 2000 database from scratch, running on a win98 machine.

 

[cmmrfrds]

The problem I had occurred on a database converted from access 97 to access 2000. What happened was access never released any of the vba code (kept in memory) I was writing so it kept consuming more and more recourses. This only occurred under Win 98 not NT which has a better memory management algorithm. To solve this I had to create a new access 2000 database and import all my objects, which cleared up the problem. Be aware that Win 98 will only use a finite amount of memory regardless of how much memory your PC has. NT will give you more memory for access to use.<br><br>It sounds like you may have something similar in that access is not releasing resources. Do you have much vba code in the app? If so, when editing vba code go up to window on the file menu and see how many code modules are open. If there is more than the one you're are editing that is a an indication resources are not being released.<br><br>I guess the obvious question is how much memory on the PC? When access was giving me the memory problem I had 256meg on my Win 98 PC and 64meg on my NT PC, and the NT did not give a memory error.

 

[HIM]

I am running this access file on a machine with 32Meg of memory. Thank you for your post. I will try it tomorrow. After all, I have everything to win, nothing to loose.

 

[cmmrfrds]

32megs is probably a little light on RAM for Access, especially if you have other applications open or services running. I would try running the app on a Win 98 PC with more RAM and see if the problem keeps occurring. Best to try on Win 98 for a valid comparison.<br><br>Gool luck,<br>Jerry

 

[HIM]

I tried on my other machine, which is Win98 as well. This machine has 64Meg RAM, and I get the same problem, except it takes longer to occur.

 

[ColinM]

You could try the office sp1?

 

[HIM]

I just tried making a new database. Just consists of four simple tables, linked togteher. Eats up the RAM faster than you can imagine.<br><br>HELP

 

[Garlic]

One thing that helps is to get rid of any objects you aren't using on your forms.&nbsp;&nbsp;Another thing is not to call any fields you aren't including on any of your forms.&nbsp;&nbsp;Cleaning leftover code might help a bit too.<br><br>Other than these things, you might consider creating a form that allows you to select a record to view before loading everything at once (this creates a filter and only shows the one you selected)<br><br>Hope this helps...

 

[aklein]

This sounds like not so much an Access problem, but a programming error, that occurs in every language ever developed.<br><br>I'll bet that you're opening some resource (a database, a recordset - something) every time through, and not closing it, ot setting it to nothing (depending upon what &quot;it&quot; is).&nbsp;&nbsp;Every time you create/open &quot;it&quot;, access allocates memory for it.&nbsp;&nbsp;Eventually you run out of memory <b>regardless of how much RAM</b> there is in the computer.<br><br>Set everything to <u>Nothing</u> before exiting the sub/function in which it's used, and close everything you open.&nbsp;&nbsp;(Don't worry about closing things you don't open.)

 

[HIM]

I can tell everybody, that this problem is a recognized problem by Microsoft. Remove all the preset styles, and you are flying.<br>A link to the paper on this problem will be found on a FAQ, this weekend.

 

[Fencefoil1]

I am having trouble with this as well. I am trying to create a new DB in Access 2K but I'll enter about 6 records and get the msg &quot;Memory Full&quot;. Memory is definately not a problem. We bought quite a bit of RAM and cleared the machine of everything we don't need. We do not get this message in any other program. After we bought additioanl memory it let us enter about 6 more records and then the same msg cam up &quot;Memory Full&quot;. Does anyone have advice for me?? Thank you in advance.