That can happen if you confuse VB with your code. I recently
had a problem that I finally traced to duplicate declarations
of a type that didn't match. VB didn't crash - it just couldn't
manage the ambiguity. Even just duplicate declares seem to
be a problem. If I'm using anything in more than one module
I declare it publicly and then comment out the private
declarations.
But that's just an example. I think that anything funky, but not
funky enough to actually raise an error when you run it, can cause
an Out Of Memory error.
--
--
Guus van Zuylen <g.*********@pinkroccade.com> wrote in message
news:88**************************@posting.google.c om...
In my VB form I am making a call to a Word object.
Sometimes, mostly in the beginning of the day I get Error 7: Out of
memory.
Memory is not the problem, perhaps it is a incompatibility with other
applications which are running:
Reflexion,
Cool:Gen
Excel
Outlook
Who knows a solution?
Guus