Yes. This involves creating an object from the MSWinsck control.

>Any ActiveX controls or external DLLs?
>
>>Ok, are there other usual suspects for memory leaks? I've looked at dangling references and such, but don't see anything like that. Or that I can tell. I could suspend right after the process ends and before it begins again to see what is open, but what am I really looking for?