XCLN: Richedit Max Chars Allowed Does Not Recognize Zero

 Last reviewed: May 5, 1997
Article ID: Q146516
The information in this article applies to:

- Microsoft Exchange Windows 95 client, versions 4.0 and 5.0 - Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0 - Microsoft Exchange Windows NT client, versions 4.0 and 5.0

SYMPTOMS

If you change the Maximum Characters Allowed setting in the Format tab of the Rich Entry Field to 0, user input will not be limited to none. What actually happens is that you can enter as many characters as you want in that Rich Entry Field. The Maximum Characters Allowed setting does not seem to effect data entry when it has a value of zero. If the value of the maximum allowed characters is set to anything other than zero, it works correctly.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft Exchange version 4.0 Windows 3.x, Windows 95, and Windows NT clients. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

To have the Rich Entry Field visible but not accept any user input, follow the steps below:

  1. Go to the General tab of the Rich Entry Field.
2. Check the 'Field is: Locked' option on that tab. 3. Regenerate and reinstall the form. 4. The Rich Entry will now be visible, but will not allow any user input.

Additional query words: Rich entry limit zero
Version : 4.0 5.0

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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.