Extracting a few selected files (For example, pgoe##.so and/or libpgicu##.so) from the client install to make an SQL connection is NOT supported.
Although it may work in some scenarios, Progress has not tested it and may produce limited or unexpected behavior.
For example,
ODBC connections generate the error message "You are not licensed to use this DataDirect Technologies product ...."Some other files from $DLC/odbc/lib are likely going to be needed as well for ssl, cursors, odbc tracing, etc ...
To establish an ODBC connection, it is necessary to have a Progress client installation.
Different Options to consider are available, depending on the Progress OpenEdge version currently in use.
OPTION 1a: OpenEdge 10.1C and laterOpenEdge 10.1C introduced a
minimal ODBC installation. This install feature
is effectively a shared network installation for the ODBC driver only and will have the smallest footprint. To install from the client machine:On the remote server with a full OpenEdge install, the necessary files are located in :
%DLC%\install\odbc A mapped drive or UNC path to this remote folder needs to be created (ie to the machine with a full installation),
From the Client's machine install the OpenEdge SQL Drivers by running:
%DLC%\install\odbc\sql-odbc-setup.exeSimilarly, the
ds-setup.exe can be run to install DataServer Drivers on the client. In effect, this is a netsetup for ODBC clients.
- This install will create a reference on the client PC pointing to the ODBC driver located on the "server", where all the files for the ODBC drivers will be on the centrally located file server.
- ODBC connections can then be created and used on the client PC as long as a network connection exists between the two machines making the driver available.
- If at any time the file server changes, the setup executable will need to be run again from each machine to update the location of the ODBC driver files.
- Existing DataSources will have outdated definitions of the location of the DLL file used by ODBC and will need to be recreated.
- The setup program cannot change existing DataSource definitions.
OPTION 1b: All Supported versionsInstall a
Shared Network Installation (netsetup) on the client PC. This will provide the client PC user with most of the license functionality available on the machine with the full OpenEdge installation, including ODBC drivers.
Both Options 1a and 1b require network connections to the machine with the full Progress installation in order to work correctly (since all files are remote) and require network connections to the machine with the full Progress installation post-install on the Client, in order to work correctly (since all files are remote). OPTION 2: OpenEdge 10.x and laterInstall the free
SQL Client Access deployment component.
The SQL Client Access installer be downloaded from the Progress Download Center, together with serial number and control codes provided for the version installed. For further information refer to Article:
OPTION 3: Progress 9.1xProgress 9 drivers are type2 ODBC wire protocol drivers that require Progress client libraries and therefore a Progress installation is needed, unlike the Type 4 drivers in later versions.
Install Client Networking (complete install) on the Client PC or t
he SQL Client Access deployment component which is available for Progress 9.x but is not free and must be ordered through Progress Sales.Optionally, a cut-down Client-Networking install detailed in Article:
