In database applications, what can an input/edit form be used for beyond simple data entry? Select the most accurate capability set.

Introduction / Context:
Business applications distinguish among forms for data entry and editing, queries for retrieval, and reports for formatted output. Understanding each component’s role avoids design mistakes and improves usability. This question asks you to identify what forms can do in addition to entering new data.

Given Data / Assumptions:

• “Form” refers to an input/edit UI bound to underlying tables or views.
• Printed or paginated output is typically produced by reporting tools.
• CRUD operations are commonly supported on forms where authorized.

Concept / Approach:
Forms are front-ends to CRUD operations. They can validate input, load existing records for edits, and, with proper permissions, delete records. While forms may provide a “print” button, the actual formatting logic for multi-page summaries, headers/footers, and group totals is handled by report layouts, not the form itself. Therefore, correct capabilities are modify and delete, not report formatting.

Step-by-Step Solution:

Verification / Alternative check:
Common platforms (Access, low-code tools, web CRUD apps) expose edit and delete buttons on forms while delegating complex print layouts to report designers.

Why Other Options Are Wrong:

• (a) or (b) alone: Incomplete—forms usually support both actions.
• (c): Report formatting is not a form’s primary function.
• (e): Incorrect because forms can modify/delete.

Common Pitfalls:
Assuming a form that prints a screen equals a true report; printed screens lack grouping, totals, and pagination controls.

Final Answer:
Modify and delete records, but not format printed reports