====================================================================== Microsoft(R) Product Support Services Application Note (Text File) WX0637: FORMS QUESTIONS & ANSWERS ====================================================================== Revision Date: 10/92 No Disk Included The following information applies to Microsoft Access(TM) version 1.0. -------------------------------------------------------------------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Microsoft | | Access and Windows are trademarks of Microsoft Corporation. | -------------------------------------------------------------------- 1. Q. How do I invoke my Microsoft Access Basic code from within a form? A. To call a function from a property, type the following: =function name() The equal sign and parentheses are required. You can call an Access Basic function from form or control properties, such as After Update or Default Value. Search for the name of a specific property in Help for examples. Subroutines cannot be called from properties. For more information, please refer to "An Introduction to Programming," Chapter 7, page 1. 2. Q. Do form rules override table rules? A. Yes, form rules do override table rules. When you position fields on a form by dragging them from the Field list, the validation property for the field inherits the validation rule that was defined for the field in the table design. 3. Q. When is it appropriate to use the exclamation point versus the period when identifying objects and properties in an expression? A. A good rule of thumb is to use the exclamation point before anything you specifically name (such as the name of your form or a control on the form) and to use a period before anything Microsoft Access names (such as a property). 4. Q. Why doesn't the header I created show in Form view? A. The header you created was most likely a page header. There are two different types of headers available on forms: form headers and page headers. A form header is displayed on-screen and when printed; a page header is displayed only when printed. 5. Q. How do I reference a control on a subform? A. To reference the subform control itself, you must use the form property of the subform control as follows: forms![master form name]![subform control name].form![control name] 6. Q. When are validation rules on a form evaluated? A. Microsoft Access evaluates a validation rule only when data is entered or edited in a field and the cursor is moved to a different field or record. If you leave the field unchanged, the validation rule is not evaluated. Microsoft Access also validates a field on a form when you leave the form, when you switch views, or when you close the form. To check for nulls, you must use a macro. For more information, please refer to Chapter 22 of the "User's Guide."