Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

How Does the Trigger Property Work in the ODBC Client Driver?

Last Update: 11/7/2018

When creating a Query device model in the ODBC Client driver, users have the option to specify a column to use as a trigger. This is the last field that will be updated when the query is refreshed, and can be used by a client application connected to the server to indicate that the record data is new. The selected column must be a field whose value will change each time that the query results in new data. There is no guarantee that the chosen field will be the last set of data sent to the server by the data source.

An example is a query that returns the progress of a sequential process. All fields in the record except a field that indicates the process step is empty. Each time the step field changes, additional fields will be updated with data. The client application may need additional processing with the new data. By setting the trigger field, users ensure that the data will be updated before the client application begins its process.

Related Products
KEPServerEX, ODBC Client