Michel,

I guess my first question is "why did you change it?". (What were you hoping to gain with this "new" way?)

My next would be "Is there anything special in the sub-exe or the main exe (like OLEPUBLIC)??

Jim N

>In my environment where an EXE is calling another EXE, I have found the following problem.
>
>Usually, in the life cycle of the main EXE, it is responsible to fire a transaction in a sub EXE and returns back to itself in wait window for the next transaction. So, the sub EXE only lives for a fraction of a second, just the time it takes to process the transaction that has been received from the main EXE.
>
>In that kind of environment, I am able to BUILD a sub EXE at any time because it is not up and running in memory all the time.
>
>But, I have found that I can't BUILD my sub EXE anymore because I have a file access denied and here's why.
>
>I just added Network=CREATEOBJECT('Network') in the startup of the sub EXE. When the sub EXE receives a transactions, it processes it as usual and returns the control back to the main EXE. However, something remains in memory which avoid me to BUILD my sub EXE. If I remove the Network=CREATEOBJECT('Network'), everything works fine.
>
>I tried RELEASE Network and even putting .NULL. into Network before releasing it and this didn't change anything.
>
>Can someone tell me what is staying in memory and what should I do to clean it up?
>
>Thanks.