Vlad,

Yup! I am still playing around with it and I am not 100% sure
how I'll finally do it. The last thing I was doing was making
the exe so that it can be called either by a normal EXE-Call
(DoubleClick, run/n, or windows Scheduler) or as a COM object
as well.

So I could let Windows Scheduler call it for the regular tasks
(toatally independend from my App) after each it will release
itself and if I need some ad hoc action, employ the object.


>If you plan to do this as completely independed process, then keep in mind that COM object will be destroyed as soon as you exit the client application, or just release all references to that COM object. This means that you require to organize this by another way. For example, some table holds a parameters for running processes. Some service aapplication looks into that table once/5 minutes and run scheduled processes when found.
>
>Another example is running a separate EXE from the COM object that will do the job, while the COM object itself is free for use and releasing without interrupting the long process.