-
I'll bet you 100 to 1 I know this one! I've had the same problem and just found the answer an hour ago! In work I've got megamemory and at home just 64.My program crashed after the 1st pass through excel at home; at work 4 times. The problem is if you create excel as an object and close it only the object dies! The excel application is still alive and not so well in your computer's memory.When you set the objects to nothing do this: excel.application.quit and it should give you your memory back.Save any variables as public if you want to pick up where you left off when you reopen excel.Hope this helped.
-
This was supposed to be an answer to this thred:
http://forums.vb-world.net/showthrea...threadid=17668
I don't know what happened. Sorry folks.
-
Here's the original post if anyone might find it helpful:
hey guys, need some help (as always)
I'm using the excel object and my program keeps crashing..
After doing a lot of processing with the ole, excel just stop responding.. I can tell because I have some traps setup to show me the processes in txt's.. Oventually excel will just stop.. and vb gets stuck in this horrible loop msgbox saying "Object stop respond.. choose and option Switch to program to fix or retry.. I can't even cancel"
Is there only so much excel can handle? Should I actually close the file and reopen it or something? Are there any commands I can tweak to give excel more room?
Any help would be great. Thanks!
