I'm running into difficulty when I instantiate a class from within an
ActiveX DLL that I have created.  It appears that the process mostly
completes, but leaves some things not done.

The high-level code is very straightforward.  Hidden from view is the
fact that there is an intricate layer of sub-sub-classes within
sub-classes within classes (possibly within collections).  The
high-level codes looks like this:

Dim xxx as clsTopObject
Set xxx = New clsTopObject

When I look at the results through the watch window, I can see where
most of the sub-classes, etc. were created properly, but some were not.
If I allow execution to continue, then, eventually, the code finds
something not initialized and it fails.

If my surmise is correct that I've run out of some resource somewhere,
my question is what do I do now?  Would it be advisable to simply break
up the ActiveX DLL into several sub-DLL's?  

Suggestions welcome.

Tom Drinkard
EDIT, Inc.
tomdrinkard@e...
(xxx) xxx-xxxx  (voice)
(xxx) xxx-xxxx  (fax)