Out Of Memory

[mans]

Hello,<br><br>I am having problems with the following error message “Out Of Memory”.&nbsp;&nbsp;I have a new computer (laptop) with 64 Meg RAM and when I have Visual Basic 6 open (and nothing else) and try to access certain forms or perform certain functions, it will not let me, at which time it displays the error message above.&nbsp;&nbsp;I have minimized all programs running in the background and increased the virtual memory without luck.<br><br>Are there any functions, controls, objects etc in Visual Basic that is causing this problem??<br><br>I would appreciate any help.<br><br>Thank You<br>

 

[JimHorton]

I've seen this occasionally...but I can only give the standard 'Microsoft Response' (to nearly all support questions, after they charge $95 per incident): &quot;Re-install.&quot;<br><br>That word has made Gates a billionaire on support calls alone!&nbsp;&nbsp;&nbsp;Anyway, I digress.&nbsp;&nbsp;That error I believe is caused by either a corrupted, missing, or incompatible dll, and reinstalling VB caused the message to go away for me on the several occasions I've encountered it.&nbsp;&nbsp;It's the sledgehammer approach--if I knew which dll it would certainly be a simpler task.<br>--Jim

 

[MikeLacey]

Is your Virtual Memory large enough? Have a look in:<br><br>Start/Settings/Control Panel/System/Performance<br><br>I have mine set to 139mb which seems to be ok. <p>Mike<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>Please don't send me email questions without posting them in Tek-Tips as well. Better yet -- Post the question in Tek-Tips and send me a note saying "Have a look at so-and-so in the thingy forum would you?"

 

[JimHorton]

mans,<br>Another thing is to check if any forms in the vbp reference a component not available, ie if you copy a project from another machine, and your box doesn't have, say, the Apex ocx, you might get this error.&nbsp;&nbsp;I recall now that I got that error for something as simple as a Rich Text Box not being referneced.&nbsp;&nbsp;If you get the project to at least open, you can set the reference.&nbsp;&nbsp;If not, you can hack the .vbp or .frm to either add the reference or remove the offending object, respectively.<br>--Jim

 

[mans]

Jim,<br><br>Thank you for your good advice.&nbsp;&nbsp;I have re-installed VB6 and examined the issue of component referencing, neither of which are the issue.<br><br>I am looking at upgrading my terminal to 128 Meg RAM anyway, that should fix the problem.<br><br>What do you think (I have already extended the virtual memory to 128) ?? <br><br>Regards

 

[JimHorton]

Neither of those are likely to help.&nbsp;&nbsp;This error usually refers to the GDI memory, or 'heap' memory, which has nothing directly to do with RAM or virtual memory.&nbsp;&nbsp;&nbsp;A machine with 16 megs should be able to open most VB projects, though it may be very slow with much paging.&nbsp;&nbsp;I'm fairly certain it's an indicator of some configuration problem, and the fact that your machine is a laptop is a red flag--these often load lots of stuff at bootup that may hog some of the heap memory.&nbsp;&nbsp;You might try and look in the Control Panel/System/Performance and see what System Resources are at bootup, then maybe check it at the time of that error.&nbsp;&nbsp;&nbsp;Typically it should be over 85% at startup.&nbsp;&nbsp;I start seeing that message in other programs when that number gets down below 50%, which usually happens the moment I open Lotus Notes :-[<br>Anyway, having 128 Megs is a good upgrade to do anyway, so that won't hurt.&nbsp;&nbsp;Let me know if it does indeed stop the error.<br>--Jim