PRB: Can't Receive Data When Using MSCOMM.OCX Control

Last reviewed: January 23, 1996
Article ID: Q141071
The information in this article applies to:

- Standard, Professional, and Enterprise Editions of Microsoft Visual

  Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

While performing serial communications by using the MSCOMM16.OCX or MSCOMM32.OCX control, you can get it to connect and send data, but not receive data.

CAUSE

You do not have the correct handshaking enabled.

RESOLUTION

To resolve this problem when using MSCOMM.OCX, set the RTSEnable property to True or add the following line of code to your program when you initialize the MSCOMM control:

   MSComm1.RTSEnable = True

MORE INFORMATION

The following information on the RTSEnable property comes from the Custom Control Help file (CTRLREF.HLP):

   (RTSEnable) Determines whether to enable the Request To Send (RTS)
   line. Typically, the Request To Send signal that requests permission to
   transmit data is sent from a computer to its attached modem.

   When RTSEnable is set to True, the Request To Send line is set to high
   (on) when the port is opened and low (off) when the port is closed. The
   Request To Send line is used in RTS/CTS hardware handshaking. The
   RTSEnable property allows you to manually poll the Request To Send line
   if you need to determine its state.


Additional reference words: 4.00 vb4win vb4all comm communication custom
KBCategory: kbprg kbprb
KBSubcategory: PrgCtrlsCus


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: January 23, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.