In the course, I will not be detailing the use of forms for inputting data into a database. The reason being, it is always user driven, and not the decision of the database designer. We will however, give a cursory review on the topic. Designing forms is critical for users who will be responsible for the day to day running of the database and have very little knowledge of the structure and design of Access databases. To help identify whether you will need an access form for a user, you will need to first answer some questions. Are you going to be the sole user of the Access database?

How many other users may be responsible for maintaining your Access database, a general users proficient with Microsoft Access and the management toolkit. Do you need to add some level of security Do you have sensitive data You need to restrict. These are just some of the common questions that need to be answered in order to allocate the amount of development time required for forms. There are four types of forms that might be needed. The four types are one, data entry input forms, which gives us users an easy interface to add, modify, and delete records, to screen inquiry forms that allow users to view as read only screens, restricting functionality and filtering for certain records. Three dialog box forms, which act as a communication interface between users and the system, passing data and values to interact with access.

For menu screen forms, which allow users to navigate around the database system without ever knowing or having access to the background design. forms can be nested, which we call a self And commonly occur with joining multiple tables together. The process is often achieved through the wizard control tool, or by setting his properties between the main form and a sub form. This now completes the section on adding data. Congratulations and well done. much information was provided, it might be useful to revisit and we do these lectures at a later date.