>>> So after the loMyClass.Method1() call, that program ends? What you should do is after the method call, set loMyClass = .NULL. to clear it from memory.
>>
>>Well, loMyClass gets out of scope when it is finished. The problem is that the class definition remains in memory. Nadya's suggestion seems to be the way to go.
>
>BTW, interestingly, I haven't used this command myself. But I've just realized a place, where I can use it. I'll check the code on Monday.

Well, so far, on this type on context, I always had those DEFINE CLASS at the framework level. However, one specific class is not bound to the framework and I prefer to have it in the sub exe. Your suggestion solves it. Whenever I come back from that sub exe, I just issue the specific command. That helps me a lot.