BUG: Carriage Return Embedded in Text When MultiLine Toggled

 Last reviewed: October 16, 1996
Article ID: Q150225
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

If the Multiline property of a Text box is toggled while in Design mode, it causes a Carriage Return to be embedded in the Text property of the Text control if the list option of the Text property is invoked while Multiline is set to True.

STATUS

Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

WORKAROUND

Delete the Carriage Return from the Text property.

MORE INFORMATION

Steps to Reproduce Problem

  1. Start a new project in Visual Basic. Form1 is created by default. Place a Text box on Form1.

  2. In the Properties window for the Text box in Visual Basic, change the Multiline property to True.

  3. In the Properties window, adjacent to the Text property, select the drop-down arrow, and type a value underneath the default Text value.

  4. Toggle the Multiline property back to False.

Note that an extraneous character appears appended to the Text property. It is safe to remove that character by highlighting it and pressing the Delete key.

Additional reference words: 4.00 vb4win vb4all buglist4.00
KBCategory: kbprg kbbuglist
KBSubcategory: PrgCtrlsStd

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