Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!olivea!uunet!mcsun!unido!rwthinf!slcdec!hippo!f1.n6000.z2.fidonet.org!p4.f36.n245.z2.fidonet.org!Norbert_Unterberg
From: Norbert_Unterberg@p4.f36.n245.z2.fidonet.org (Norbert Unterberg)
Newsgroups: comp.windows.ms.programmer
Subject: comp.windows.ms
Message-ID: <1393185243@p4.f36.n245.z2.fidonet.org>
Date: 6 May 91 09:31:00 GMT
References: <41388@fmsrl7.UUCP>
Reply-To: Norbert_Unterberg%p4.f36.n245.z2@hippo.dfv.rwth-aachen.de (Norbert Unterberg)
Organization: Point of SoftStream, Dortmund, Germany
Lines: 21
Comment-To: Bengt_A._Palsson@f1.n6000.z2.fidonet.org (Bengt A. Palsson)


 >   1)   Is there a way to activate (start up) one application (that is NOT
 >        currently running), and then terminate it FROM another application
 >        that is currently running ?
 >
 >   For example:   I have applications X, Y and Z. X is currently running and
 >                  wants Y or Z to start running, perform a task and then
 >                  terminate.

Yes, there is. First X trys to establish a DDE connection to Y. If Y does not 
answer, you start it using the WinExec or LoadModule command. That also makes Y 
the active window. After that, the DDE link between X and Y should work. X 
tells Y what to do, and after the processing X terminates Y (also by a DDE 
command).
A window (Y) thar receices (DDE-) messages does not automatically popup. It has 
to make itself the active window. If Y has finished its job, it can either tell 
it X, so X can popup again (via SetActiveWindow), or it can terminate or 
SetActiveWindow(x) itself.

Norbert, 2:245/36.4