ODBC Client Driver for TOP Server

Part Number:   41233169-N  
Domestic Price:   US$1629
Availability:   In Stock - Ships in 0 to 1 days.
Delivery Method:   CD and/or Online Delivery (shipping costs apply)
Includes:   Perpetual License to use the server and drivers in this suite on a single computer with no artificial limits on number of devices, tags, or connected client applications. You own this license and it will continue to operate without payment of any other annual fees. Price shown includes 1 year of email/phone support and upgrades. If you want access to email & phone technical support after first year, you may renew maintenance, otherwise there are no hidden recurring fees.

The TOP Server ODBC client driver reads data out of any ODBC compliant database (i.e. text, Access, SQL Server, Sybase, Oracle, etc) and exposes the data as OPC items. Once setup as OPC items, any HMI/SCADA or other system that is an OPC client can read the data.
OPC Compliance LogoBecause this product is part of the TOP Server family, it can bring in database data and provide it as OPC items to OPC clients and also provide it via Suitelink to Wonderware and to Intellution as a native Intellution driver.

To learn more about the TOP Server family of products, we strongly encourage you to visit the TOP Server focus site at www.toolboxopc.com. Below are full details on this specific member of the TOP Server family:

ODBC Specific Features

  • Multiple connection sessions to multiple ODBC data sources
  • Reading and writing to the SQL engine
  • Auto tag generation based on tables, queries and stored procedures from your ODBC data source - simplifies setup and saves you significant engineering time and money.
  • Support for "Execute" statements within the Query access method.
  • Execute tag for executing queries (e.g. Channel.Device.Execute).
  • 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.
ODBC Data Access Methods

This driver can read data out of databases in 3 different ways - tables, queries, and stored procedures, as described below:


There are two methods for retrieving data from an ODBC data source table; Fixed Table and Dynamic Table.

Fixed Table

This access method allows you to access each item in the ODBC data source table. After creating a device using the specified Fixed Table method, the driver will create tags in the server´s tag database that correspond to each item in the ODBC data source table.

Dynamic Table

The Dynamic Table access method allows you to access a single record set in an ODBC data source table via record tags. The record tags correspond to their respective columns in the data source table. These record tags are dynamically controlled via internal control tags, accessible from a client application, to allow you to work with a particular record set in the table. Below are a list of the internal control tags that you can use to access your data.

Queries The ODBC client driver supports SELECT queries in which you can define and create a tag database tailored to your needs. You can retrieve tags of whole tables all the way down to specific records.

Using the Query access method

To retrieve tags based on a query, you must first type a SELECT query in the query window. Once you have entered in a query that will return some results, select the "Validate" button. If you do not receive an error message then the query is valid and you may then select the "Apply" button (if you are using the device wizard then select the "Next" button). Once the query passes validation, a tag database will be created based on the query. If there is an error with the query or the data source connection, a message box will appear stating the reason for the validation failure. If you receive an error message, fix the query or data source connection and try the validation again.

Note: The driver must have access to the database via ODBC for the query to execute properly.

Stored Procedures

The ODBC client driver supports access to stored procedures. Guidelines for accessing stored procedures on your ODBC data source are as follows:

  • The data source must support stored procedures.
  • At least one custom stored procedure needs to be contained and tested by the data source before attempting to create the tag database and connect to it via the ODBC client driver.
  • The current account must have permission to access the stored procedure.
  • The driver must have access to the data source via ODBC for it to access the stored procedure and execute it properly.