1. More on Tables Open your table in design view Click here!

2. 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

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

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

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

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

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

8. But they can be frustrating Create your own clever messages!

9. Lookup: choose value from a list

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

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

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

13. Create a “lookup table” Just like before…

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

15. Lookup table is the Row Source

16. Add some categories

17. Now the choices can grow

18. Limit to List?

19. 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)