ODBC Client

Subscription $578/yr Pay an annual fee to use the software. Support & Maintenance is included. Add to Cart Added

Your cart cannot contain both a Subscription and a Perpetual product.

Please modify your cart to add this license type.

Add to Cart
Perpetual $1725 Pay a one-time product list price. Mandatory year-one Support & Maintenance Agreement is included. Add to Cart Added

Your cart cannot contain both a Subscription and a Perpetual product.

Please modify your cart to add this license type.

Add to Cart

Product Overview

The ODBC Client driver provides single-point access to multiple ODBC data sources via Open DataBase Connectivity (ODBC). The goal of ODBC is to make it possible to gather any data from any application, regardless of which database management system (DBMS) is handling the data. Using the power and speed of OPC, Kepware is able to offer ODBC data to any OPC/DDE enabled client and ensures data integrity through extensive error handling.

  • Clients may reside Locally or Remotely
  • Clients can communicate via OPC
  • Supports read and write access to multiple ODBC-compliant databases
  • Supports read and write to SQL engine
  • Write to BIGINT stored procedure inputs
  • Supports four access methods, including fixed table, dynamic table, query, and stored procedure
  • Supports automatic tag generation based on tables, queries, and stored procedures from your ODBC data source
  • Supports automatic generation of SQL type 'NCHAR' as OPC type 'string'
  • Simple interface enables users to get their data immediately
  • Microsoft Access
  • Microsoft SQL
  • MySql
  • Oracle
  • Sybase
  • English
  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Clients
  • SuiteLink and FastDDE for Wonderware



  • Fixed an issue where stored procedure OUT string parameters were not cleared before the stored procedure was executed.



  • Increased the maximum length of a stored procedure parameter from 255 to 1023 characters.



  • Fixed a bug where MySQL stored procedures fail to execute.
  • Fixed an issue where millisecond resolution for DATETIME input types is lost when executing a stored procedure.


  • Fixed an issue where MySQL stored procedures failed to execute using the ODBC Client driver.


  • Resolved an issue where MySQL stored procedures failed to execute. The issue was mistakenly introduced with the enhancements made in the 5.19 release.



  • Added support for "Execute" statements within the Query access method.
  • Added an Execute tag for executing queries (e.g. Channel.Device.Execute).
  • Added the ability to enable or disable the query time interval. This allows users to exclusively trigger queries on demand via the device’s Execute tag.
  • Resolved an issue where a change in the query interval setting did not persist through shutdown and restart.
  • Removed duplicate messages that occurred in the event log when automatically generating tags.
  • Resolved issue with handling “money” and “smallmoney” data types as parameters to stored procedures in the stored procedure access methods.
  • Resolved an issue with the Update Tags button on the query and stored procedure access methods.
  • Resolved a configuration issue where a device prevents editing and reports that it is processing tags when no client references to the device exist.



  • Increased the maximum number of channels from 100 to 256.
  • Updated the driver so that it will not force the access of tags added manually to be Read Only when the Set write access for imported database tags option is unchecked. This option only applies during automatic tag generation.
  • Updated automatic tag generation to force the internal tags that should be Read Only to be Read Only.



  • Fixed an issue with incorrect Boolean conversion handling. Booleans can now be set and cleared properly.


  • Fixed an issue where certain queries would result in bad quality for all tags in the device. The driver would post the "Unable to open recordset on device (Reason: Query timeout expired)" error message in the Event Log. This issue was due to an unnecessary query being used to count the number of items in the table.


  • Fixed an issue with queries wherein the driver failed to read tags if the query included a UNION.
  • The EnableMiscellaneousQuerySettings registry setting was broken in 5x due to the separation of the Runtime and Configuration. The registry setting was removed, and the dialog page made visible to all users. A related wizard page was also added.


  • Fixed an issue where the time stamps from reads of Oracle 10g failed because the returned string includes microsecond resolution. We now truncate the string to place it in a known format.
  • The ODBC Client driver is capable of communicating with many applications that support the standard "ODBC" or MyODBC data source format.
  • Microsoft Data Access Components (MDAC) is required. MDAC consists of several core components that provide various database technologies; including ODBC and its drivers.