19 years ago
object which is memory (in SW) without actually making the object
active doc, i.e.
Set Part = swApp.ActivateDoc(ObjectName)?
The problem I am running into is in very large assemblies (400+
discrete parts) I am seeing failures (SW Automation failures) as I
loop thru each objects (in this case I parse for parts only) using the
Set Part = NextDoc call. I am beginning to think it might be a memory
leak as performance/speed degrades the further into the loop I get.