More on Tables• Open your table in design view

Click here!

Fields have properties• Properties control what data can be entered and how it will

be displayed (at least in datasheet view)

This box explains what each property

does

Field properties are important• You should be familiar with ALL of them• Size: How many characters of text are allowed?

Default values can be set• This field will be “true” unless changed by the user

Required input?• If “yes”, you can’t save data unless this field is filled

Input masks can prevent typos• What about international postal codes and phone numbers?

Validation rules are useful...• Use the expression builder to test data for validity

But they can be frustrating• Create your own clever messages!

Lookup: choose value from a list

Value List• choices “hard coded” into the field properties• best for value lists that NEVER change (Male, Female)

Value list, cont.• I chose a “combo box” to display my list (this, that, other)• Note the default value (=“activity”)

Lookup from a table• Use table/query if your list of values will change

Create a “lookup table”• Just like before…

Lookup tables can be simple• One field (or two): Description (& ID or code) • Give the table a clear name

Lookup table is the Row Source

Add some categories

Now the choices can grow

Limit to List?

Control is easy, but has a price• Input masks, validation rules, and lookup tables prevent

user errors

• Input contols are ESSENTIAL for data quality, BUT...

• They can be very frustrating for users

• They may require frequent maintenance (updating & repair)