What is the primary purpose of forms and reports in a database application?

What is the primary purpose of forms and reports in a database application?

• A. Forms format data for printing or viewing; reports provide data entry and editing.
• B. Forms provide data entry and user interaction; reports format and present data for printing or viewing.
• C. Forms store data, while reports define database structure.
• D. Forms and reports are interchangeable tools for data entry.

Answer: (B)

The concept being tested is how a database application separates input from output: forms are the user-facing tools for entering and interacting with data, while reports are designed to present data in a formatted way for printing or viewing. Forms provide fields, controls, validation, and navigation so you can add, edit, or review records easily. Reports take data from the tables and arrange it with headings, groupings, totals, and layout formatting so you can read it comfortably or share it in a print-friendly form. That’s why the correct description fits: forms handle data entry and user interaction, while reports format and present data for printing or viewing. The other ideas mix up these roles: formatting for printing is the job of reports, not forms; data entry is the job of forms, not reports; storing data or defining database structure is done by tables and the overall schema, not by forms or reports; and saying they’re interchangeable ignores the distinct tasks each tool is designed to support. For example, you’d use a form to enter a new customer, and a report to show sales totals by month that can be printed.

The concept being tested is how a database application separates input from output: forms are the user-facing tools for entering and interacting with data, while reports are designed to present data in a formatted way for printing or viewing. Forms provide fields, controls, validation, and navigation so you can add, edit, or review records easily. Reports take data from the tables and arrange it with headings, groupings, totals, and layout formatting so you can read it comfortably or share it in a print-friendly form.

That’s why the correct description fits: forms handle data entry and user interaction, while reports format and present data for printing or viewing. The other ideas mix up these roles: formatting for printing is the job of reports, not forms; data entry is the job of forms, not reports; storing data or defining database structure is done by tables and the overall schema, not by forms or reports; and saying they’re interchangeable ignores the distinct tasks each tool is designed to support. For example, you’d use a form to enter a new customer, and a report to show sales totals by month that can be printed.