Since MS had a fix back in 2001 for this I'm going to assume it's been addressed since then. Is that a reasonable assumption?
http://support.microsoft.com/kb/286504 Since others make references to this as a known problem though I'm still a little nervous. Maybe I'll have to try some testing. Bob --- In [email protected], "George Henne" <g...@...> wrote: > > Answers inline... > : > >2. Current script runtime: has the CreateObject()-related memory leak > >ever been addressed? Is it truly related to using Set X = Nothing or a > >general problem with object disposal (i.e. including object references > >going out of scope)? > > CreateObject is built into VBScript. We always use AddObject - we have > not investigated CreateObject. -- You received this message because you are subscribed to the Google Groups "nsb-ce" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nsb-ce?hl=en.
