How to Access Live xBase Data in Power Automate Desktop via ODBC



The CData ODBC Driver for xBase enables you to integrate xBase data into workflows built using Microsoft Power Automate Desktop.

The CData ODBC Driver for xBase enables you to access live xBase data in workflow automation tools like Power Automate. This article shows how to integrate xBase data into a simple workflow, moving xBase data into a CSV file.

Through optimized data processing, CData ODBC Drivers offer unmatched performance for interacting with live xBase data in Microsoft Power Automate. When you issue complex SQL queries from Power Automate to xBase, the driver pushes supported SQL operations, like filters and aggregations, directly to xBase and utilizes the embedded SQL engine to process unsupported operations client-side (e.g. SQL functions and JOIN operations).

Connect to xBase as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

The DataSource property must be set to the name of the folder that contains the .dbf files. Specify the IncludeFiles property to work with xBase table files having extensions that differ from .dbf. Specify multiple extensions in a comma-separated list.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing workflows.

Integrate xBase Data into Power Automate Workflows

After configuring the DSN for xBase, you are ready to integrate xBase data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

In the flow editor, you can add the actions to connect to xBase, query xBase using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Actions -> Database) and configure the properties.

  • Connection string: DSN=CData xBase Source

After configuring the action, click Save.

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Actions -> Database) and configure the properties.

  • Get connection by: SQL connection variable
  • SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
  • SQL statement: SELECT * FROM Invoices

After configuring the action, click Save.

Add a Write to CSV File Action

Add a "Write to CSV file" action (Actions -> File) and configure the properties.

  • Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
  • File path: set to a file on disk
  • Configure Advanced settings as needed.

After configuring the action, click Save.

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Actions -> Database) and configure the properties.

  • SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the action, click Save.

Save & Run the Flow

Once you have configured all the actions for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

Now you have a workflow to move xBase data into a CSV file.

With the CData ODBC Driver for xBase, you get live connectivity to xBase data within your Microsoft Power Automate workflows.

Related Power Automate Articles

This article walks through using the CData ODBC Driver for xBase with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

Ready to get started?

Download a free trial of the xBase ODBC Driver to get started:

 Download Now

Learn more:

xBase-Compatible Databases Icon xBase ODBC Driver

The xBase ODBC Driver is a powerful tool that allows you to connect with live xBase- compatible databases, directly from any applications that support ODBC connectivity.

Access xBase databases like FoxPro & Clipper (.dbf, .ndx, .ntx, .dbt, etc) from virtually anywhere through a standard ODBC Driver interface.