ACC: Null Field's Input Mask Behaves Differently Than Expected

Last reviewed: May 30, 1997
Article ID: Q147200
The information in this article applies to:
  • Microsoft Access versions 2.0, 7.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you use the TAB key to move to a null field that has an input mask, the input mask does not appear until you begin typing data.

RESOLUTION

If you want the input mask to appear when you use the TAB key to move to a null field, you can create an event procedure that sets the field automatically to Edit mode. This will cause the input mask to appear. The basic steps to do so are as follows:

  1. Create a form based on your table with the input mask and open it in Design view.

  2. Select the form control bound to the input mask field and view its properties.

  3. Set the OnGotFocus property [Event Procedure] to the following procedure by using the Code builder:

          SendKeys "{F2}"
    

  4. Save and close the module.

  5. View the form in Form view. Note that as you press TAB to move to the null field with an input mask, the input mask appears.

STATUS

This behavior is by design.

REFERENCES

For more information about input masks, search on the phrase "input mask," and then view "InputMask Property" using the Answer Wizard from the Microsoft Access for Windows 95 Help menu.


Additional query words: display input-mask
Keywords : GnlInpt kbusage
Version : 2.0 7.0
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


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