If you are an independent developer, you might think of this as your on-call quality assurance team. All developers know that a fresh set of eyes can be very effective at finding errors that are overlooked. And, it saves a lot of time to catch them early in the process. Well, this feature can flag common errors as they are made. You can't get more timely feedback than this. In addition to flagging errors, the process will even offer solutions.
Since multiple errors can simultaneously occur on the same object, the errors will be ranked from highest to lowest priority. By clicking the error indicator, you can correct or ignore each error. Figure 3-2 shows an example of multiple errors on one control.
Sometimes you just don't want to hear about everything that Access thinks is an error. Access provides the options to not only turn error checking on and off but to specify the settings. This allows you to limit the types of errors that are flagged. You can even select the color used to flag errors. To set these options, once again, choose Options from the Tools menu and then select Error Checking. Figure 3-3 shows how to specify which errors should be flagged.
The common error scenarios that are flagged include the following.
□ Unassociated label and control—When a label and a control are selected but they are not associated with each other.
□ New unassociated label—If a label is added to a form or control and it is not associated with any control.
□ Invalid control source—The control source property is not a valid expression or field name, the expression specified does not start with "=", or the expression refers to the control itself—a circular reference.
□ Duplicate Option values—The Option value property is not unique in the option group.
□ Keyboard shortcut errors—Such as an unassociated label with a keyboard shortcut, a label or control that has a shortcut that is already associated with another label or control, and a space character as a shortcut key.
□ Invalid sorting and grouping definitions for a report.
□ Report width greater than page width.
Was this article helpful?