Office integration, presentations and simple databases
Office and Technology Applications asks you to match a task to the right tool and to predict what a feature will do. This independent chapter covers spreadsheets, word processing, presentation design, simple databases, collaboration and file formats without asserting an official target blueprint or product-version interface.
Core rules
- Spreadsheet formulas begin with =; functions use name(arguments), such as =SUM(B2:B10). Relative references (A1) shift when copied; absolute references ($A$1) do not; mixed references lock only the row or column.
- In automatic calculation mode, a spreadsheet updates dependent formulas when precedent values change. Manual calculation settings differ. Circular references can indicate an unintended dependency, but some applications permit explicitly configured iterative models; do not assume every cycle is always an error.
- Word processing features: styles apply consistent formatting and build navigation; mail merge combines a main document with a data source; track changes records edits; PDF is designed for fixed-layout distribution; editing is possible with suitable tools, while the source document is usually more useful for structural revision.
- Presentation best practice: one idea per slide, readable contrast, alt text for images, and slide notes for detail you do not want on screen.
- Databases store structured records; a query answers a question, a form supports data entry, and a report formats output.
- Collaboration via shared drives or cloud documents raises version-control and permission questions; least privilege means share view-only unless editing is needed.
Worked example
A price list has tax rate in C1. Cells B2:B10 hold prices. You need after-tax prices in D2:D10. Enter =B2*(1+$C$1) in D2 and copy down. B2 is relative, so D3 uses B3. $C$1 is absolute, so every row still points to the tax rate. Copying =B2*(1+C1) without dollar signs would make D3 use C2, an empty cell, producing wrong results. Reasoning: identify what must stay fixed, then lock it.
Traps
- Confusing COUNT (numbers) with COUNTA (nonblank) and COUNTIF (conditional).
- Assuming a fixed-layout PDF necessarily preserves all editable source-document structure; actual capabilities depend on the file and tool.
- Treating mail merge as copy-and-paste; it requires a data source with matching field names.
- Choosing a chart type that hides the pattern: pie charts for parts of one whole, line charts for trends over time, bar charts for comparisons.
- Forgetting that formulas, not typed results, update when data changes.
Presentation and data responsibilities
A slide master and layouts can coordinate shared design for slides that use them; not every pasted or differently mastered object will follow automatically. Keep a presentation focused on its audience and evidence. Use readable contrast and appropriate descriptive labels, and ensure that a chart’s source and units remain clear after copying. Presenter notes support the speaker and are different from text intended for the audience. Rehearse the actual delivery and output path, including fonts, media and any offline requirements, rather than assuming that a file opening on one laptop proves compatibility everywhere.
For a simple database, distinguish the stored table from a form used for entry, a query used to select or calculate and a report used to present output. A primary key identifies rows; related records can use a foreign key under declared constraints. Design field types and required values from the actual records. A spreadsheet with repeated headings is not automatically a well-designed relational schema. Linking office objects can retain an update relationship, whereas embedding copies content into the destination under the application’s model. Check whether a linked file remains accessible to recipients and whether refreshing can disclose information that should not be shared. These are conceptual user-computing skills, not a live software installation or a replica of an official practical examination.