The information in this article applies to:
Advanced: Requires expert coding, interoperability, and multiuser skills. This article applies to a Microsoft Access database (.mdb) and a Microsoft Access project (.adp). SUMMARYThis article shows you how to substitute your own custom message for the generic error message that occurs when you violate an input mask on a form. The generic error message for input mask violation is:
MORE INFORMATIONMicrosoft provides programming examples for illustration only, without warranty
either expressed or implied, including, but not limited to, the implied warranties of
merchantability and/or fitness for a particular purpose. This article assumes that you
are familiar with the programming language being demonstrated and the tools used to
create and debug procedures. Microsoft support professionals can help explain the functionality
of a particular procedure, but they will not modify these examples to provide added
functionality or construct procedures to meet your specific needs. If you have limited
programming experience, you may want to contact a Microsoft Certified Solution Provider
or the Microsoft fee-based consulting line at (800) 936-5200. For more information about
Microsoft Certified Solution Providers, please see the following page on the World Wide Web:
http://www.microsoft.com/mcsp/For more information about the support options available from Microsoft, please see the following page on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspYou can trap input mask violations and substitute your custom error message for the generic error message in the form's Error event. The following sample Visual Basic code demonstrates this method:
Setting the Response parameter to acDataErrContinue lets you ignore the error and continue without displaying the default error message. You can then supply a custom error message in place of the default.If you have multiple controls on your form with different input masks, you can use Screen.ActiveControl.Name to get the name of the control causing the error. The following sample code demonstrates this method for a form with phone number, social security number, and ZIP code fields:
REFERENCESFor more information about On Error event procedures, in the Visual Basic Editor, click
Microsoft Visual Basic Help on the Help menu, type "error event - event procedures" in
the Office Assistant or the Answer Wizard, and then click Search to
view the topic. Additional query words: inf
Keywords : kbusage kbdta AccCon KbVBA |
Last Reviewed: July 6, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |