Skip to content

Database

OLEDB Integration

Zynk's OLEDB integration connects workflows to data reached through an OLE DB provider, such as Microsoft Access databases, Excel workbooks and SQL Server. SQL tasks select rows as XML, update records, return single values or repeat steps for each row, so that data moves into Sage 200, Magento, Business Central or QuickBooks without manual exports.

Available for

Capabilities may differ depending on the product.

Benefits

Why businesses connect OLEDB

Workbooks and Access files as live sources

Price lists kept in Excel and departmental Access databases become proper data sources. Zynk reads them through the provider installed on the server, so nobody has to save, rename and upload files by hand.

Connection settings you control

Each connection is defined by a provider, a data source and its properties, mirroring a standard OLE DB connection string. Pointing a workflow at a test copy or the live file is a matter of changing the source.

Results shaped for the next step

Execute Select Query turns the rows a query returns into XML, using the root and row element names you set. Accounting, ecommerce and ERP import tasks can consume that file as it stands.

Processing row by row

The OLEDB Repeater runs a block of tasks for every row returned and exposes column values as variables. A single line in a workbook can become its own order, email or API call.

Updates written back

Execute Query runs insert, update and delete statements, so a workflow can mark rows as exported or store the document number another system returns. Execute Scalar Query fetches one value, such as a row count, to decide what happens next.

Capabilities

What you can do with OLEDB

Every task the Zynk OLEDB connector can run, grouped by the direction data moves.

Actions in OLEDB

Tasks Zynk can automate in OLEDB

4 tasks

  • Execute query → in OLEDB
  • Execute scalar query → in OLEDB
  • Execute select query → in OLEDB
  • OLEDB repeater → in OLEDB

Need something that isn't listed?

Most OLEDB projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate OLEDB?

A lot of operational data never makes it into a proper system. It sits in an Access database built years ago or a shared Excel workbook that one person maintains. Moving it into the accounts or the web store depends on copy and paste, and errors creep in every time someone does it.

Without integration

  • Prices copied from a spreadsheet into the web store line by line
  • Orders logged in an Access database and retyped into the ledger
  • No way to tell which rows have already been sent
  • A process that depends on one person's spreadsheet routine

With Zynk

  • Workbook rows are read by query and imported as prices
  • Access records pass straight to the accounting system's import tasks
  • An update statement marks each row once it has been handled
  • A scheduled workflow with logging and error alerts

How it works

How the OLEDB integration works

  1. Step 1: Install the provider

    Make sure the right OLE DB provider is installed where Zynk runs, such as the Access Database Engine for Access and Excel files or Microsoft's OLE DB driver for SQL Server.

  2. Step 2: Create the connection

    Enter the provider name, the data source path or server and any properties the provider needs, such as the Excel file version or whether the first row holds column headers.

  3. Step 3: Build the queries

    Write SQL for each step or use the query designer, adding parameters so the same statement can run for a date range, a branch or a single customer.

  4. Step 4: Join it to the workflow

    Pass results to import tasks for systems such as Sage 200 or Magento, schedule the run and write a status back to the source so no row is processed twice.

Example use cases for OLEDB integration

OLEDB and Sage 200

Read sales orders or customer records from an Access database and import them into Sage 200, then keep stock records exported from Sage 200 in the database for local use.

From OLEDB to Sage 200:Sales orders, CustomersFrom Sage 200 to OLEDB:Stock records

View the Sage 200 integration →

OLEDB and Magento

Use an Excel price workbook as the source for Magento tier and special prices, and keep a local copy of Magento orders for analysis outside the store.

From OLEDB to Magento:PricesFrom Magento to OLEDB:Orders

View the Magento integration →

OLEDB and Microsoft Dynamics 365 Business Central

Load items and customers maintained in Access or Excel into Business Central, and write posted sales invoices back to a reporting database.

From OLEDB to Microsoft Dynamics 365 Business Central:Items, CustomersFrom Microsoft Dynamics 365 Business Central to OLEDB:Sales invoices

View the Microsoft Dynamics 365 Business Central integration →

OLEDB and QuickBooks

Create QuickBooks Online customers and invoices from rows in a spreadsheet or database, and keep exported payments in a table finance can query.

From OLEDB to QuickBooks:Customers, InvoicesFrom QuickBooks to OLEDB:Payments

View the QuickBooks integration →

Find your integration →

OLEDB integration FAQs

What is the difference between OLEDB and ODBC in Zynk?
Both connectors run the same kinds of SQL tasks. ODBC connects through a data source name and an ODBC driver, while OLEDB uses an OLE DB provider and connection string. Pick whichever your data source supports best; Access and Excel files are common OLEDB sources.
Can Zynk read an Excel workbook through OLEDB?
Yes. With the Access Database Engine provider installed, a workbook can be queried much like a database, with each worksheet treated as a table. Zynk also has an Excel connector that converts workbooks to CSV or XML if you prefer a file-based approach.
Can Zynk connect a Microsoft Access database to Sage?
Yes. Query the Access tables that hold orders, customers or products and pass the results to Sage 50 or Sage 200 import tasks. An update query can then mark each row as posted, giving you a clear trail of what was sent.
How much SQL do OLEDB workflows need?
Every OLEDB task runs a statement, so a working knowledge of SQL is useful when you maintain the workflow yourself. The query designer helps with select statements, and our team can write the queries when we build the integration.
Which systems can OLEDB data be sent to?
Any system Zynk connects to. Typical destinations are accounting and ERP packages such as Sage 200, Business Central and QuickBooks, and ecommerce platforms such as Magento, where workbook prices or stock figures need importing regularly.
Can I loop through each row in a spreadsheet?
Yes. The OLEDB Repeater runs a set of sub-tasks for every row a query returns, with each column available to the tasks inside. One row could become an order in Sage, an email to a customer or a product update in Magento.
How do I get an OLEDB workflow started?
Tell us where the data lives, whether in Access, Excel or another OLE DB source, and which system needs it. We'll confirm the provider required and outline the queries and workflow steps to automate the transfer.

See what Zynk can automate for your OLEDB setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a callSee pricing →