> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/microsoft-access-input/options-microsoft-access-input/content-tab-microsoft-access-input.md).

# Content tab

Use the **Content** tab to control the output filename.

![Microsoft Access input step Content tab](https://2745965000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvZoINBz5C5WnDZQlbOJQ%2Fuploads%2Fgit-blob-e0a41b96ef5f3b428e013fadbd10469d4af407d2%2FPDI%20Microsoft%20Access%20input%20step%20Content%20tab.png?alt=media)

| Option                            | Description                                                                                                                                                                                                        |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Table**                         | Specify the name of the Access table from which you want to read data. Click **Get tables** to query the database for the list of table names.                                                                     |
| **Include filename in output?**   | Select the checkbox and specify a field name to include the file name (string) in the output of the Microsoft Access input step.                                                                                   |
| **Include table name in output?** | Select the checkbox and specify a field name to include the table name (string) in the output of the Microsoft Access input step.                                                                                  |
| **Include rownum in output?**     | Select the checkbox and specify a field name to include the row number (Integer) in the output of the Microsoft Access input step.                                                                                 |
| **Reset rownum per file?**        | Select the checkbox to set the row number to 1 in each file that is being read.                                                                                                                                    |
| **Limit**                         | Specify an integer larger than zero to limit the number of rows read by the Microsoft Access input step.                                                                                                           |
| **Add filename to result?**       | Select the checkbox to add the Access filenames read to the result of this transformation. A unique list is kept in memory that can be used in the next job entry in a job, for example in another transformation. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/microsoft-access-input/options-microsoft-access-input/content-tab-microsoft-access-input.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.