By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,082 Members | 2,108 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,082 IT Pros & Developers. It's quick & easy.

MS Access Validation Rules

P: 2
I am really stuck some of my validations in [u]Database are not working. I need examples of working Range Check validations which I can use. Someone please help me!
Feb 7 '07 #1
Share this Question
Share on Google+
3 Replies

Expert 2.5K+
P: 3,532
You're really going to have to give us a bit more of an explanation of what you're trying to do, Cherish, in order for us to help you.
Feb 7 '07 #2

Expert Mod 10K+
P: 14,534
I am really stuck some of my validations in [u]Database are not working. I need examples of working Range Check validations which I can use. Someone please help me!
Date range

Expand|Select|Wrap|Line Numbers
  1. =BETWEEN #01/01/2005# AND #01/01/2006
Number range

Expand|Select|Wrap|Line Numbers
  1. > 10 And < 100
This is the best I can do without a lot more information.
Feb 8 '07 #3

Expert Mod 15k+
P: 31,494
As the others have already said, you need to follow the instructions in POSTING GUIDELINES: Please read carefully before posting to a forum to post a meaningful question that we can help with.

In the mean-time, this may help...
ValidationRule, ValidationText Properties

You can use the ValidationRule property to specify requirements for data entered into a record, field, or control. When data is entered that violates the ValidationRule setting, you can use the ValidationText property to specify the message to be displayed to the user.

Note The ValidationRule and ValidationText properties don't apply to check box, option button, or toggle button controls when they are in an option group. They apply only to the option group itself.


Enter an expression for the ValidationRule property setting and text for the ValidationText property setting. The maximum length for the ValidationRule property setting is 2048 characters. The maximum length for the ValidationText property setting is 255 characters.

For controls, you can set the ValidationRule property to any valid expression. For field and record validation rules, the expression can't contain user-defined functions, domain aggregate or aggregate functions, the Eval function, or CurrentUser method, or references to forms, queries, or tables. In addition, field validation rules can't contain references to other fields. For records, expressions can include references to fields in that table.

You can set the ValidationRule and ValidationText properties by using:

The Field Properties section of table Design view (for a field validation rule).

The property sheet for a table by clicking Properties on the View menu in table Design view (for a record validation rule).

The property sheet for a control on a form.

A macro or Visual Basic. In Visual Basic, use a string expression to set these properties.

For table fields and records, you can also set these properties in Visual Basic by using the DAO ValidationRule property.


Microsoft Access automatically validates values based on a field's data type; for example, Microsoft Access doesn't allow text in a numeric field. You can set rules that are more specific by using the ValidationRule property.

If you set the ValidationRule property but not the ValidationText property, Microsoft Access displays a standard error message when the validation rule is violated. If you set the ValidationText property, the text you enter is displayed as the error message.

For example, when a record is added for a new employee, you can enter a ValidationRule property requiring that the value in the employee's StartDate field fall between the company's founding date and the current date. If the date entered isn't in this range, you can display the ValidationText property message: "Start date is incorrect."

If you create a control by dragging a field from the field list, the field's validation rule remains in effect, although it isn't displayed in the control's ValidationRule property box in the property sheet. This is because a field's validation rule is inherited by a control bound to that field.

Control, field, and record validation rules are applied as follows:

Validation rules you set for fields and controls are applied when you edit the data and the focus leaves the field or control.

Validation rules for records are applied when you move to another record.

If you create validation rules for both a field and a control bound to the field, both validation rules are applied when you edit data and the focus leaves the control.

The following table contains expression examples for the ValidationRule and ValidationText properties.

ValidationRule property ValidationText property
<> 0 Entry must be a nonzero value.
> 1000 Or Is Null Entry must be blank or greater than 1000.
Like "A????" Entry must be 5 characters and begin with the letter "A".
>= #1/1/96# And <#1/1/97# Entry must be a date in 1996.
DLookup("CustomerID", "Customers", "CustomerID = Forms!Customers!CustomerID") Is Null Entry must be a unique CustomerID (domain aggregate functions are allowed only for form-level validation).

If you create a validation rule for a field, Microsoft Access doesn't normally allow a Null value to be stored in the field. If you want to allow a Null value, add "Is Null" to the validation rule, as in "<> 8 Or Is Null" and make sure the Required property is set to No.

You can't set field or record validation rules for tables created outside Microsoft Access (for example, dBASE, Paradox, or SQL Server). For these kinds of tables, you can create validation rules for controls only.
Feb 8 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.