windows odbc client for progress databases

Progress updates an index at the end of any statement in which it changes the values for one or more index fields. At the end of the transaction in which Progress creates the record. When Progress releases the record from the record buffer.

When Progress processes a VALIDATE statement. At the end of the closest iterating subtransaction block in which the Progress 4GL creates the record. At the end of a statement in which Progress assigns values to all components of the index entry. Progress creates a new index entry for a record at the first occurrence of any one of the following: Explain what are the scenarios or situations under which Progress Database creates new index entry for a record?Īs you work with your application, you will want to know when Progress creates and updates indexes. infrastructure, this is driven instead by the logical structure and nature of your database connectivity requirements.ĩ. The prime function of your OpenLink Components does not determine their physical location within your I.T. OpenLink Database Agents (the files 'pro63e_sv' or 'pro73c_sv' or 'pro82a_sv' depending on major and minor Progress Database Server version and sub-version number)

OpenLink Request Broker (the file 'oplrqb' or 'oplrqb.exe' depending on operating system) Server Components (OpenLink Database Agent Service Providers) Generic UDBC Driver (the end product of statically linking the file libudbc.o or dynamically linking the file 'libudbc.so' or libudbc.sl' under UNIX) Generic Driver for JDBC (the files 'opljdbc.zip' or 'oplj dbc.jar') Generic ODBC Driver (the file 'oplodb32.dll' under windows or OS/2, 'oplodbc.sl' or 'oplodbc.so' under UNIX) Your OpenLink Data Access Driver Suite (Multi-Tier Edition) consists of the following components, subdivided by prime function:Ĭlient Components (OpenLink Database Agent Service Consumers)

Windows odbc client for progress databases