ACC: Name Property Change Not Accepted with Case Change Only

Last reviewed: August 22, 1997
Article ID: Q121673
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

When you change a control's Name property setting, the change is not accepted if you change only the setting's case. For example, if you change the setting "Text0" to "text0" the change will not be accepted.

CAUSE

Case-only changes are not accepted because the property is not case sensitive.

RESOLUTION

To change a control's Name property setting, you must change something other than just the case of the setting. Replace a character with another character, add a character, or delete a character. Then, change the setting again, changing it to the text you want.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 1.x, 2.0, 7.0, and 97. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Start Microsoft Access and open any database.

  2. Create a new, blank form.

  3. Add a text box to the form.

  4. Change the text box control's Name property from "Text0" to "text0" (in Microsoft Access 1.x and 2.0, change the Name property from "Field0" to "field0"), and then press ENTER. Note that the change is not accepted.


Additional query words: capital capitalize lower small
Keywords : FmsProp kbusage
Version : WINDOWS:1.0,1.1,2.0,7.0,97
Platform : WINDOWS
Hardware : x86
Issue type : kbbug
Solution Type : kbworkaround


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