Hmmm. OK thanks, George.

From what I can tell, wwXML does not create global variables, but also does not seem to be overly rigourous about declaring all object variables local and doing ManualGarbageCollection, which I always tend to take to extremes as I've always been on NT and as we know is not very tolerant of objects hanging around.

However, I do have it from Erik Moore that wwXML object references should be going out of scope properly and that it is probably related to this FOR/EACH problem, but again, these references are not globally defined either. They are locally instantiated and either should go out of scope or get released by .NULL.. I suppose I could instantiate wwXML at the _SCREEN level and just make my calls to that. Can I still temporarily create a local reference so I'm not having to refer to it as _SCREEN. everywhere?

Thanks again for the reply. This is a nasty problem indeed.

- Randy

>>I could definitely use a solution to this, if even just a workaround. I'm trying to use wwXML class as is from West-Wind and am having this problem. My only solution to make sure things get cleaned up after doing my XMLToObject calls is to shut the app down, which I *really* don't want to do.
>>
>>I can't believe this would not be causing headaches for others doing this type of stuff, unless those unknown datasessions just don't cause any problems for anyone. However, I would think that over time, the dreaded c5 could rear it's ugly head, right?
>>
>Randy,
>
>I believe a KB article is in the works. The only solution that I found was to issue CLEAR ALL. It was one of the reasons, I completely junked using any global variables in favor of adding properties/objects to the _SCREEN. They're unaffected by this.