Overview
OverviewKepware's 32 bit ODBC Client driver works in conjunction with our OPC Server KEPServerEX, to provide single-point access to multiple ODBC data sources via ODBC (Open DataBase Connectivity). 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, KEPServerEX is able to offer ODBC data to any OPC/DDE enabled client. Data integrity is ensured with our extensive error handling.
Devices
Supported DevicesDatabases:
- Microsoft Access
- Microsoft SQL
- Oracle
- Sybase
- MySql
The ODBC Client Driver is capable of communicating with any application that supports the standard "ODBC" or MyODBC data source format.
Required: MDAC - Microsoft Data Access Components (it consists of several core components that provide various database technologies; including ODBC and its drivers.)
Features
Specific Driver Features
SpecificSpecific Driver Features
GeneralGeneral Driver Features
OPC/DDEOPC/DDE Features
Learn more about OPC - Open Process Control HMI/ClientHMI/Client FeaturesKEPServerEX has been enhanced to provide the widest range of connectivity of any server product available. KEPServerEX supports the following client server technologies:
To see a list of HMI's and Clients that we support go to our HMI / Client Support page. |
Required
Required Software and HardwareSupported Operating Systems
- Windows NT
- Windows 2000
- Windows Server 2003
- Windows XP
PC Hardware
Minimum- 400 Mhz Pentium CPU
- 128 Megs of RAM
- 100 Megs of Free Hard Drive Space
Recommended
- 600 Mhz Pentium CPU
- 512 Megs of RAM
- 100 Megs of Free Hard Drive Space
Hardware Requirements
- For Device and Hardware Requirements see the Devices tab.
- Hardware Accessories
Protocol
Communication Protocol- ODBC API - Open DataBase Connectivity Application Programming Interface
VB
Visual Basic- KEPServerEX Visual Basic OPC Client
- Complex and Simple Visual Basic OPC Client Examples
- Using Modems and Visual Basic with KEPServerEX.
- Download the Modem and VB Example with Source Code
- Knowledge Base
Help
Help/LinksRevisions
ODBC Client Driver OPC Driver Revisions| Driver updates below coincide with Server Release V4.280.435.0 (04/30/08) |
| ODBC Client Driver (V4.35.61.0) |
| - Fixed issue where the values written to the tags of a stored procedure get reset when the last active client referencing those tags disconnects from the server. A new device property "Reinitialize stored procedure when the last tag referenced is removed" has been added for this purpose, while at the same time retaining backward compatibility. - Since on the fly stored procedure modification are not allowed, we now properly disable all UI controls on the stored procedure device page if a client is connected. - Fixed issue where the device property "Maximum records to import" is always '1' for tables (in a SQL server) that have a space in their names. - Fixed issue where tags were orphaned (subsequent reads from the client will fail) for a device when another device with the exact same name (on a different channel) is deleted from the server project. |
| Driver updates below coincide with Server Release V4.270.416.0 (09/27/07) |
| All Drivers |
| - Fixed issue where server menu buttons like 'New', 'Open', 'Exit' would become permanently disabled when attempting to perform auto tag generation on a driver that had missing runtime dependencies. - Fixed issue that could occur when multiple items with the same scan rate are read by exception and another item is added/asynchronously read/removed at that same rate. This issue resulted in stale data for those tags read by exception. |
| Driver updates below coincide with Server Release V4.264.401 (06/01/07) |
| All Drivers |
| - Fixed issue in the driver library where it was possible to delete a tag prior to stopping it. This would result in the accessing of invalid memory which could eventually result in an exception that would prevent a channel from processing any tags. |
| ODBC Client Driver (V4.35.52) |
| - Added an enhancement (device option) to clear the inputs after the stored procedure has been executed (i.e. set the current cached value to a good default for its data type). The device option is in the form of a 'sticky' checkbox. The default is to *not* clear the inputs after execution; after the device is created the wizard 'remembers' the last selection via the registry and defaults the next new device's 'clear inputs' selection to that last value. - Added auto-generation of SQL type 'NCHAR' as OPC type 'string'. - Added support for writing to BIGINT stored procedure inputs. - Fixed issue where when adding system tags manually, the data type defaulted to 'String' instead of 'Long' or 'Bool'. - Fixed issue where system tags were allowed for query access method. - Fixed issue where adding system tag for stored procedure access method from the client, resulted in ReadOnly access instead of ReadWrite for the tag. - Added support for writing to NCHAR stored procedure inputs, in addition to the existing support for writing NVARCHAR and NLONGVARCHAR. |
| Driver updates below coincide with Server Release V4.222.376 (01/26/07) |
| ODBC Client Driver (V4.21.45) |
| - Fixed issue high CPU utilization when multiple tables with very large record counts are referenced. |
| Driver updates below coincide with Server Release V4.210.367 (11/17/06) |
| All Drivers |
| - Fixed issue where a rapid sequence of item add, sync read, and item remove requests could result in bad OPC quality for some items included in a block sync read and/or sync read timeouts. - Fixed issue with Unsolicited UDP Mode Ethernet Encapsulation mode, where driver would stop receiving unsolicited messages after sending a message. |
| Driver updates below coincide with Server Release V4.201.359 (07/19/06) |
| ODBC Client Driver(V4.11.42) |
| - Fixed issue where we would not properly initialize the stored procedure name at runtime prior to performing an execute on the store procedure. This could occur if a write to the execute command was received prior to fully initializing the stored procedure.
- Fixed issue where we would post an "unable to read stored procedure parameter" error message prior to fully initializing the stored procedure. |
| Driver updates below coincide with Server Release V4.200.353 (03/24/06) |
| ODBC Client Driver (V4.10.39) |
| - Added support for MySQL.
- Fixed anomaly that could occur if a remote SQL server PC is powered off and/or we lose communications. - Fixed issues with reporting incorrect data for fixed table elements that are out of range. This can occur if records are deleted from a table, and fixed table indices that are greater than the record count are accessed. We now properly set the quality to bad for records that are out of range. - Fixed runtime issues where changes to DSN (Channel Properties), selected table, and/or selected query would not take effect until the project was shutdown and re-opened. - Fixed runtime issues where changes to selected stored procedure would not take effect until the project was shutdown and re-opened. - Fixed runtime issues where changes to DSN selected query would not take effect until the project was shutdown and re-opened. - Added ability to manually update (generate) the tags associated with a stored procedure. - Added ability to manually update (generate) the tags associated with a query. |
| Driver updates below coincide with Server Release V4.150.304 (11/12/04) |
| ODBC Client Driver (V4.03.23) |
| - Fixed incorrect write failure on the stored procedure _Execute tag
when the execute command succeeds.
- Fixed issue with dynamic table _RecordCount tag reporting bad quality if the table is empty. The server now return 0 with good quality. - Fixed failure to automatically create a tag database for dynamic tables that reference an empty table. - Fixed an unnecessary error message from being logged when reading data from an empty dynamic table and the selected record has not been advance to something greater than 0. |
| Driver updates below coincide with Server Release V4.130.287 (5/28/04) |
| ODBC Client Driver (V4.02.21) |
| - Fixed issues related to misreading data from tables where some columns contain data types not supported by our driver. |
| Driver updates below coincide with Server Release V4.110.270 (3/22/04) |
| All Drivers |
| - Library fix affecting all drivers. |
| Driver updates below coincide with Server Release V4.102.251 (9/25/03) |
| ODBC Client Driver (V4.01.17) |
| - Fixed issues with addresses that reference table (fixed and dynamic) data, where a dot ('.') is in the table name (i.e., we also use this as a field delimiter) |
| Driver updates below coincide with Server Release V4.100.239 (7/10/03) |
| ODBC Client Driver (V4.00.16) |
| - New Driver |