>Hi,
> Thank you for reply.
>
>>>Do you need to set properties or pass parameters?
>Yes, I need to pass certain parameter to it.
>
>>>Will you be calling it once or several times?
>hmm.... It is just a part of my application which will be called by 2 standard EXE - my management system and task schedule (I develop it by myself).
>
>>>Is this the only application that needs to call the module or could there be more?
>No, 2 application as mentioned as above!!
>
>
>Again, I have another question. Any way to not pending after calling the OUT OF PROCRESS EXE or standard EXE?
>
>Thank you

Sounds like this is a candidate for an out of process exe that exposes the functionality through COM classes.

It also sounds like you already created such program. Normally when an out of process COM exe is called it runs on a separate process and does not prevent the client application from going about its business. If the client app needs a notification of when the COM exe is done then you can do this using asynchronous call-backs and / or events.

See "Asynchronous call-backs and events" in the component tools guide from MSDN. It has a very easy to follow example of how to create such a thing.