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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access 2000 out of memory

Status
Not open for further replies.

cmmrfrds

Programmer
Feb 13, 2000
4,690
US
I have an access MDB with about 80 forms of which most have some VBA code. Also, about 35 Funtions of VBA code and all the data is in a separate MDB. The total app after compacting is 2.7 megs. It has got to the point where whenever I go into VBA code it gives an out of memory error. I am running Access 2000 on a PC with Win 98 and 128 meg of RAM on a 500 hertz pentium 3. I am letting Windows manage the virtual memory on the PC.<br>
I sent the app to a friend who has 384 meg of RAM on a 500 hertz pentium 3 and he can edit the VBA code. <br>
<br>
Are there memory limits in Access 2000 I can tweak? Help!!!!!! Has anybody else had this experience?
 
I supsect your VBA code is corrupted.<br>
It happens especially with the amount of VBA code you have.<br>
If a form is corrupted there is no hope for it period.<br>
Compacting it made it worse.<br>
<br>
Now to fix it.<br>
Create a new .MDB and Import the tables queries and anything that will come over.<br>
Forms with corrupted VBA code will not come over.<br>
If you can open them in design view in your original .mdb. Great. If not they will need to be re-created from scatch.<br>
Keep everyone else out of it until you are done.<br>
When you have it back working again then make a .MDE<br>
It will never crash again.<br>
When you want to make changes open the .MDB then change it and make a new .MDE. Your uses will use th e.MDE<br>
Rename the .MDB to something differnt or else they wil open it again by mistake.<br>
<br>
In order to use a .MDE the tables Must be in a backend.<br>
So in the fixed .MDB link all of the tables.<br>
<br>
I've been where you are at dozens of times.<br>
Its no picnic.<br>
But the only hope in the future is the .MDE<br>
<br>
BACKUP your data regularly.<br>
<br>
<br>
<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
 
Thanks Doug. A couple of things. First, I tried to make an MDE of the file and was able to do so okay. I seem to be able to traverse the app okay, it is just when I try to enter the VBA code on this PC. I have another PC that, my kids are using, which has NT installed and 64 meg of RAM. I can open and edit the app on that PC, so far, 2 NT PC's can open and work with the app. Is Win 98 my problem?? Also, the PC is an HP Pavilion pentium III. I was hoping it wasn't necessary to invest in another copy of NT and it's hardware related issues.<br>
<br>
If my code was corrupted, wouldn't it also fail in the NT environment?
 
I guess you know you can not edit certain things in a .MDE one of them being VBA.<br>
the other is a report.<br>
You can make a macro and new queries, and add tables but nothing to do with VBA or programing.<br>
No, Win '98 is not a problem<br>
It could be some file that VBA needs is bad on that machine.<br>
Also make sure you have all of the options set in VBA editor. I don't have 2000 here in front of me but look on your other PC's and compare it. Its in the Add-ins I think.<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
 
Doug, here is the current status.<br>
I called HP support -- actually got living breathing person, and they had me run msconfig on my PC and delete a number of start up services. I unchecked a number of items such as; config.sys, autoexec, load =, run=, some win.ini options, and a couple of others.<br>
<br>
I worked in Access 2000 for 15 minutes and didn't loose any system resources. It is still too early to tell, but this may have fixed the problem. I could sure use a success today.<br>
<br>
I will post if the problem continues.<br>
<br>
Thank you
 
Update:<br>
I have worked in Access, created forms, functions, and have been in/out several times over the last hour. The system resources are holding at the same %, which did not happen before -- the resources gradually diminished.<br>
<br>
The problem appears to be the way HP had configured Win 98 on my PC<br>
<br>
Although, I have a new, hopefully simple problem. I have a measurement field in my table where numeric values of some integer such as 240 or a decimal value such as 3.123 or .156778 can be entered. I can't seem to set the field to accept a variable number of decimal digits. When I go into the table by double clicking on the table and then try to enter a numeric value it always truncates the decimals or if I put fixed decimal places it holds the position but replaces my decimal digits with zeroes.<br>
<br>
Any thoughts on this?<br>
<br>
Thank you again.
 
What field type? If field type is Integer or Long Integer you can't store decimal data (but you CAN display it as if it contained decimal digits). Switch to Single or Double. <p>Jim Conrad<br><a href=mailto:jconrad3@visteon.com>jconrad3@visteon.com</a><br><a href= > </a><br>
 
Yes Jim is right, an Integer is defined as whole number between -32,768 to 32,767<br>
so keep that in mind when designing databases if your number ever goes above or below 32,767 you can not use it anyway Decimal or not.<br>
<br>
Single and Double can have decimal points and Single goes from -3.402823E38 to -1.401298E-45 for negative values and from 1.401298E-45 to 3.402823E38 for positive <br>
<br>
Double<br>
-1.79769313486232E308 to -4.94065645841247E-324 for negative values and from 4.94065645841247E-324 to 1.79769313486232E308 for positive values <p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
 
Thank you both. <br>
<br>
I switched to double and it works great.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top