SAMPLE: Using RegisterWindowMessage for Interapp Communication

Last reviewed: February 15, 1996
Article ID: Q66246
The information in this article applies to:
  • Microsoft Windows Software Development Kit (SDK) for Windows versions 3.0 and 3.1

The RegisterWindowMessage() function associates a unique message number with a given message name. This message number is guaranteed to be unique throughout the system but may change between Windows sessions. The new message is typically used for communication between two cooperating applications.

Using RegisterWindowMessage() is an alternative to using DDE to communicate between two or more applications. This technique is most useful if the information to be passed between applications can be contained in the wParam and/or lParam parameter of the message.

A sample application is available that demonstrates how to implement communication between two cooperating applications, using RegisterWindowMessage().

Download TWINS.EXE, a self-extracting file, from the Microsoft Software Library (MSL) on the following services:

  • Microsoft Download Service (MSDL)

          Dial (206) 936-6735 to connect to MSDL
          Download TWINS.EXE (size: 24241 bytes) 
    
  • Internet (anonymous FTP)

          ftp ftp.microsoft.com
          Change to the \SOFTLIB\MSLFILES directory
          Get TWINS.EXE (size: 24241 bytes) 
    


Additional reference words: 3.00 3.10 softlib TWINS.EXE
KBCategory: kbprg kbfile
KBSubcategory: UsrMsg


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 15, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.