Pre-Installation Requirements for the Single-Tier "Lite" Edition ODBC Driver for Progress/ OpenEdge, for Windows
DBMS Requirements
You need to know a variety of information pertaining to your target Progress/
- The Progress Startup Mode (Sockets or Shared Memory)
- The Single-Tier driver cannot connect over Shared Memory, so you may need to restart your Progress database in sockets mode
- Once running in Sockets mode, you need to know the TCP socket service name and/or port number
- The Single-Tier driver cannot connect over Shared Memory, so you may need to restart your Progress database in sockets mode
- The Progress SQL Engine Capabilities at Startup (4GL, SQL, Both)
- Progress 8 and earlier engines only support 4GL, and you can only use our SQL-89 drivers
- Progress 9 engines support both 4GL and SQL, and you can use either our SQL-89 or SQL-92 drivers
-
OpenEdge 10 and later engines only support SQL, and you can only use our SQL-92 drivers
- Progress 8 and earlier engines only support 4GL, and you can only use our SQL-89 drivers
- Your Progress database server's hostname or IP address
- Your Progress database tcp socket service name and port number
- Whether or not your database queries fire 4GL triggers (primarily a concern for SQL-89 connections)
- Whether or not your database queries involve Array fields (primarily a concern for SQL-89 connections)
Software Requirements
- Progress Client layer
To connect to this DBMS Version You need these components ... ...on the same host as these Progress OpenEdge 10.x or later Progress® SQL-92 Client Access SQL-92 Lite Drivers Progress 8.x or earlier Progress® Client Networking SQL-89 Lite Drivers Progress 9.x in SQL-89 or 4GL mode Progress® Client Networking SQL-89 Lite Drivers Progress 9.x in SQL-92 mode Progress® SQL-92 Client Access SQL-92 Lite Drivers
- The Progress® Client Networking or Progress® SQL-92 Client Access must be licensed from Progress Software.
OpenLink Software cannot provide such licenses.
- Installers for Progress® Client Networking or Progress® SQL-92 Client Access must be obtained from your Progress distribution media or the Progress Web site.
OpenLink Software cannot provide such installers.
- The Progress® Client Networking or Progress® SQL-92 Client Access must be licensed from Progress Software.
- SQL-89 vs SQL-92
- The SQL-89 drivers are Progress version-specific, with names like Multi-Threaded ODBC Driver for Progress 9.1D or Single-Threaded ODBC Driver for Progress 8.3E.
These drivers offer support for Progress triggers, Progress Distributed Databases (i.e., connections to multiple databases over a single ODBC connection), our specialized tableview configuration, and a particular presentation of Progress array data familiar to the Progress community.
SQL-92 drivers, which all specify "(SQL-92)" in their name, do not support SQL-89/4GL functionality.
- The SQL-92 drivers have a more generic branding such as Multi-Threaded ODBC Driver for Progress 9.1 (SQL-92).
These drivers enable SQL-92 queries against Progress 9.x and later, including
OpenEdge 10.x and later. SQL-89 drivers, which all specify a "letter" version of Progress (e.g., 8.3C, 9.1B) do not support SQL-92 functionality.
- The SQL-89 drivers are Progress version-specific, with names like Multi-Threaded ODBC Driver for Progress 9.1D or Single-Threaded ODBC Driver for Progress 8.3E.
These drivers offer support for Progress triggers, Progress Distributed Databases (i.e., connections to multiple databases over a single ODBC connection), our specialized tableview configuration, and a particular presentation of Progress array data familiar to the Progress community.
SQL-92 drivers, which all specify "(SQL-92)" in their name, do not support SQL-89/4GL functionality.
- 32-bit vs 64-bit
- 32-bit Progress Clients can only be used with 32-bit Single-Tier drivers, which can only be used with 32-bit client applications.
- 64-bit Progress Clients can only be used with 64-bit Single-Tier drivers, which can only be used with 64-bit client applications.
- If your components do not all match "bitness," open a Support Case for assistance in selecting the best path forward, e.g.,
- If available, getting the Progress Client of the required "bitness";
- If available, getting a client application of the required "bitness"; or
- If the bitness-matched Progress Client and ODBC client application do not exist, changing to a bitness-bridging ODBC driver.
- If available, getting the Progress Client of the required "bitness";
- 32-bit Progress Clients can only be used with 32-bit Single-Tier drivers, which can only be used with 32-bit client applications.
Configuration Requirements
- Ensure that the local Progress Client Networking connects to the target Progress DBMS.
Next...
- Proceed to Installation Documentation
Referenced by...