>COM and Distributed C O M are only essential if you require communication between your processes. A poor mans alternative available on NT (& probably Win2K) is the AT command, which allows you to specify the machine that you want to run your executable on e.g.
>
>RUN AT \\MachineName "MyExe param1 param2"
>
>You may also have to specify the time, etc. This will only work if the NT Schedule Service is running and User access rights may also have to be sorted out.
>
>Just an idea.

Why do you call it a "poor mans alternative"?

That's a nice idea! Although I would need to create an all new EXE with all the necessary functions in it and configure all the computers I might want to run it on accordingly shoudn't I? Either way (using COM or this method), I need to configure a lot of stuff so they both seem valid.

One question comes to mind though, can I build a DCOM server using FoxPro (or should I build it using C++ and all it's wizards)? Plus, is it easy to build clients in FoxPro that'll communicate with DCOM objects written in another language?