Exporting Data: Spreadsheet, Text, CSV, XML & PDF
Key Takeaways
- Tables and query results can be exported to a spreadsheet, a text file (.txt or .csv), or XML.
- A spreadsheet export supports further calculations, charts, or pivot-table analysis outside the database.
- A text (.txt/.csv) export is the most universal, simplest format for sharing raw data with other systems.
- XML export preserves tagged structure, useful for exchanging data between dissimilar systems.
- Reports are normally exported to PDF, which preserves the finished layout, grouping, and formatting exactly.
Exporting Data: Spreadsheet, Text, CSV, XML & PDF
Once information has been retrieved or presented inside the database application, it is often needed outside it -- in a spreadsheet for further analysis, as a plain file to import into another system, or as a polished document to share with someone who does not have the database software at all. Exporting is how a database moves data (and reports) out into these other formats.
Why Export Matters
Exporting is different from printing: printing produces a paper (or paper-like) copy of what is on screen, while exporting produces a separate file in another format that other applications can open and work with. The exam expects you to know which database objects export to which formats, and why each format is used.
Exporting a Table or Query Result
Both tables and query results can be exported directly out of the database application. The three destination formats to know are:
| Export format | Typical file type | Why you would use it |
|---|---|---|
| Spreadsheet | e.g. .xlsx | To do further calculations, charting, or pivot-table analysis outside the database |
| Text file | .txt or .csv | A simple, universal format for sharing raw data with almost any other system, including non-database software |
| XML | .xml | A structured, tagged format used to exchange data reliably between very different systems and applications |
- A spreadsheet export is the natural choice when the data needs formulas, charts, or further number-crunching that is easier in spreadsheet software than in the database itself.
- A text export (.txt or comma-separated .csv) strips the data down to its simplest, most portable form -- every value separated by a delimiter such as a comma -- which makes it the safest choice when the destination application's exact format is unknown or very different from the database.
- An XML export preserves more structure than a plain text file (field names and record boundaries are explicitly tagged), which makes it useful for exchanging data between different database or web systems that both understand XML.
Because these three formats apply to tables and query results, exporting is one of the clearest ways the exam tests whether you know the difference between raw/retrieved data (tables, queries) and formatted presentation output (reports).
Exporting a Report
Reports are different: because a report's whole purpose is a polished, fixed layout meant for reading or printing, the standard export destination for a report is PDF. A PDF export freezes the report's layout -- fonts, spacing, headers/footers, grouping, and summary calculations all display exactly as designed -- regardless of what software or device opens the file. This is why PDF is the expected answer whenever an exam question asks how a report (rather than a table or query) is normally shared electronically: spreadsheet, text, and XML exports preserve raw values, but a PDF preserves the finished, formatted presentation.
Choosing the Right Export Format
A useful way to remember this for the exam is to separate the objects from their formats:
- Table or query -> Spreadsheet, Text (.txt/.csv), or XML -- because the goal is moving the underlying data somewhere else for reuse.
- Report -> PDF -- because the goal is preserving the finished presentation exactly as designed.
If a question describes wanting to reuse the numbers in another program, the answer points toward a spreadsheet, text, or XML export of a table or query. If a question describes wanting to send someone a finished, ready-to-read document that looks the same on any device, the answer points toward exporting a report to PDF.
How Exporting Fits with the Rest of the Module
Exporting sits at the end of the data lifecycle covered by this module: data is entered into tables (Category 3), refined and retrieved with filters and queries (Category 4), optionally viewed and edited through forms (Category 5), and finally presented and shared through reports and exports (this category). Recognizing which stage a question is describing -- raw storage, retrieval, entry, or output -- is often the fastest way to identify the correct object or command among the answer choices.
The General Export Workflow
Even though the destination formats differ, the exam expects the same general sequence for exporting any object:
- Select the object to export -- a table, a query result, or a report.
- Choose the export command and pick the destination format (spreadsheet, text, XML, or PDF).
- Confirm the destination and file name, and specify a save location.
- Complete the export, producing a brand-new file separate from the database.
The exported file is a snapshot of the data (or layout) at the moment of export. If the underlying table, query, or report changes afterward, the previously exported file does not update automatically -- a fresh export is needed to capture the new information. This matters when a question describes needing "up to date" figures outside the database: the export has to be repeated, not just reopened.
Exam Tips
- Table/query -> spreadsheet, text, or XML. Report -> PDF. This single rule resolves most export questions.
- .txt and .csv are both text-file export options -- .csv simply uses commas to separate field values.
- XML export preserves structure (tags for fields/records), which is why it is favored for exchanging data between dissimilar systems.
- Exporting creates a new, separate file; it does not alter the original table, query, or report inside the database.
Which file format is most appropriate for sharing raw table data with almost any other application, regardless of what software it uses?
A finished report needs to be shared so it looks exactly the same, with all formatting and grouping intact, no matter what device opens it. Which export format should be used?