bugs, vb 6.0 build error. error while creating an executable

I have a VB 6.0 Application. It used to work fine for years. Now, when
I was trying to compile I get the error "H80004005(-2147467259)
Unspecified Error." And If I Click OK then pops up a message, "Out of
Memory"

Any help is appreciated.
Thanks,
-Harry,

"Out of Memory" is just VB's way of admitting it has NO CLUE what happened.
That makes it essentially useless for diagnostics.

Try again immediately after a reboot.


Bob
--

But there ARE some specific reasons why you might get this.

1. Are you by any chance using MSForms2 in your VB app? MSForms is known
to cause this error. It's not intended for use in VB.
2. Have you added any new code since you last compiled? If so, you might
have exceeded VB limitation of the size of a module.
3. After re-reading your message, is this really a "VB runtime" error or is
it a "Windows" error? I ask because of the Unspecified Error you get before
the Out of Memory error. You probably need to fix the first error because
the 2nd error (the Out of Memory one) might be a result of the first error.
IOW, the first error has caused your program to become unstable so it chokes
and you get the out of memory.
4. Going to #2, if you undo your code changes, do you still get the error?
If not, then you've pinpointed the problem to the new code you've added so
that's what you need to focus your attention on.
5. Has ANYTHING about your dev PC changed? Any new programs installed?
Any updates (particularly Windows service packs, Office, and IE or any
service packs for Office or IE)?

--
Mike
Microsoft MVP Visual Basic

All good ideas. I would add:
6. Have you added any param definitions like this. This will cause an error
during compile
Sub SomeSub(Optional SomeValue as Variant = null)
7. Check the task manager during a compile, is it using all the available
memory? (VB that is not the task manager :-) If so you might have an overuse
of nested types.
8. Goto http://mikesdriveway.com/code and download the C2 project. It will
pinpoint which module in your app is causing the error. This will at least
narrow the problem down.

Michael