>>>>Ok, no problem. May be it happened because my manager ran the TxtToPDF from the server? And may be that program has its own memory leak. But he was able to run the previous version quite successfully with only one problem: he ran it with set deleted off.
>>>
>>>I'm not sure about this, but I doubt if the program run from the server will be differents (crashing the apps) from run locally. Unless, there is something wrong with the network connection. It's more make sense if the program itself has a leak (maybe). Or maybe there are other things that involves for crashing the apps. Well, I don't know...
>>
>>But you're pretty sure it's not LaunchAppAnWait in its current version, right?
>
>Yup. The most critical one is closing the handle, that's it.

Ok. That's the version I currently have in our Common_Utility program. My manager is running the previous version of this program right now since that one gave him a problem. I think, he'll have the same memory problem later on.