Error:"Out of Memory" in VB6. {RESOLVED}

Hello Everyone,

When i opend my application in vb6.0, it gives messge

"Out of memory" . I do not see any problem. My app contains atleast 15 forms, 30 classes and 6 modules. But that shoul not be problem.

Does anybody has any idea or same experince? Plase provide your feedback.

Thanks in advance

Hdave

Reboot?

I tried to reinstall Visual Basic 6.0. Still it is gives same error:

"Runt time error: 7
"Out of Memory"

I do not have any clue. Why it is doing? What could be problem? is it anything related with database interface or connectivity or use of COM or OLE automation?

I do not see any problem. But i am not able to run my application.

Please, help me out. I have trying since two days. Provide your feedback.

Thanks lot.

Hdave

Does it only happen on this one project?

Just thought about if it is only one project, then you may be able
to get around it by re-creating the .vbp file. Sometimes they get
corrupted even though they look ok when you open them with
notepad. I ran into something like this, but it wouldnt compile
only crash during compile. So I created a new .vbp by creating a
new project, then adding all the references, forms, modules, and
classes. Then I saved it as the original file name (all this in a
different folder, copy all the forms,etc to this new folder). Tested
and it worked. Maybe this will work for you too?

I am trying your way. Let us see. I will send you reply.

Thanks man.

HDave

thumb:
Thanks very much man!!! Now it is working. But i do not see any reason why .vbp file got corrupted?

Hdave:)

No prob.

As long as its working now, guess that is what really matters.

Dont forget to resolve both threads.

Later.

hello
ur vb6 some dll muzt me currupted
first remove (uninstall) vb6 completly
and then install it as a new .................

Quote:

---

Originally posted by hdave
thumb:
Thanks very much man!!! Now it is working. But i do not see any reason why .vbp file got corrupted?

Hdave:)

---

vaishu999, did you read this post?
Only on one project so it's not a corrupted vb dll. Probably
happens when vb crashed or the project was closed down
incorrectly.

{RESOLVED}

Hi RobDog888

yes i saw this u r right this error is due to project not close properly or when any project run somtimes we not close no. of recordsets and connections command objects that why it creats
lot of temp files it slows vb and when too much load created then its currepts dlls so vb can't open single project due to no. of temp files in memory

thanks RobDog888
vaishu