# Microsoft Access input The **Microsoft Access input** step reads data from Microsoft Access database files in `.mdb` or `.accdb` format. ### Step name The default **Step name** is **Microsoft Access input**. You can change it. ### Preview rows Select **Preview rows** to examine the contents of the Access input file specified in **File or directory**. Preview helps you confirm that your settings return the rows you expect. ### Configure the step (tabs) The **Microsoft Access input** step includes the following configuration tabs: * **Files** * **Content** * **Fields** * **Additional output fields** #### Files tab Use the **Files** tab to select input files. ![Microsoft Access input step File tab](/files/GtaolIGubYnCUGSSyhiJ) | Option | Description | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Filename is defined in a field?** | Accept filenames from previous steps. | | **Get filename from field** | Field that contains the filenames at runtime. | | **File or directory** | Location (or location and name) of the input database file. Select **Add** or **Browse** to add the file, directory, or wildcard combination to **Selected files**. | | **Regular expression** | Regular expression used to select files from **File or directory**. | | **Exclude regular expression** | Regular expression used to exclude files from **File or directory**. | | **Selected files** | List of files and directories selected. You can select a row and use **Edit** to update wildcards, mark whether the file is required, and include subfolders. If a required file is not found, PDI generates an error. | | **Show filename(s) button** | Displays a list of all files to load based on the settings in this tab. | #### Content tab Use the **Content** tab to choose the Access table and control additional output fields. ![Microsoft Access input step Content tab](/files/6lDVQcXVZPo3sY3x7FPG) | Option | Description | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Table** | Access table to read from. Select **Get tables** to query the database for table names. | | **Include filename in output?** | Adds the file name (string) to the output. Specify the output field name. | | **Include table name in output?** | Adds the table name (string) to the output. Specify the output field name. | | **Include rownum in output?** | Adds the row number (Integer) to the output. Specify the output field name. | | **Reset rownum per file?** | Resets the row number to 1 for each file read. | | **Limit** | Limits the number of rows read. Use an integer larger than zero. | | **Add filename to result?** | Adds Access filenames read to the transformation result. A unique list is kept in memory and can be used by downstream job entries (for example, another transformation). | #### Fields tab Use the **Fields** tab to define field selection and conversion. ![Microsoft Access input step Fields tab](/files/FG6yrjJnUM3dFNAsH1Rk) | Option | Description | | -------------- | -------------------------------------------------------------------------------------- | | **Name** | Output field name. | | **Column** | Column name in the Access table. | | **Type** | Target data type to convert to. | | **Format** | Format or conversion mask used during conversion. | | **Length** | Output data type length. | | **Precision** | Output data type precision. | | **Currency** | Currency symbol used during conversion. | | **Decimal** | Decimal symbol used during conversion. | | **Group** | Grouping symbol used during conversion. | | **Trim type** | Trimming behavior used during conversion. | | **Repeat** | Select **Y** to repeat the previous row’s value if the column value is empty (`null`). | | **Get fields** | Select **Get Fields** to populate the table from the source file. | #### Additional output fields tab Use the **Additional output fields** tab to add file metadata to the output. ![Microsoft Access input step Additional output fields tab](/files/dVrtVRlywm0sbPvdENaD) | Option | Description | | --------------------------- | --------------------------------------- | | **Short filename field** | File name without path, with extension. | | **Extension field** | File name extension. | | **Path field** | Path in operating system format. | | **Size field** | File size. | | **Is hidden field** | Whether the file is hidden (Boolean). | | **Last modification field** | Last modified date/time. | | **Uri field** | File URI. | | **Root uri field** | Root part of the URI. | ### Metadata injection support This step supports metadata injection. You can use it with [ETL metadata injection](/pdia-data-integration/pdi-transformation-steps-reference-overview/etl-metadata-injection.md) to pass metadata to your transformation at runtime. Supported fields include (by tab): * **File tab**: Filename is defined in a field, Get filename from field, File or directory, Regular expression, Exclude regular expression, Required, Include subfolders * **Content tab**: Table, Include filename in output?, Include tablename in output?, Include rownum in output?, Filename fieldname, Tablename fieldname, Rownum fieldname, Reset rownum per file?, Limit, Add filename to result * **Fields tab**: Name, Column, Type, Length, Precision, Trim type, Format, Currency, Decimal, Group, Repeat --- # Agent Instructions: 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: ``` GET https://docs.pentaho.com/pdia-data-integration/pdi-transformation-steps-reference-overview/microsoft-access-input.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.