General Connectivity Rules:
- Client products to Server products with one Major version back are supported.
- Client products to Application Server products with one Major version back and one version forward are supported.
- Server to Server products: Apply the previous rule, as one Server product behaves as a Client for the other.
- Any shared memory connection, is only allowed if the version of the Client products and Server products match exactly, otherwise connection has to be client/server.
The following combinations of components from the Progress 9.1x and OpenEdge 10.x release cycles are supported.
Where Progress 9.1x components are forward compatible with OpenEdge 10.x components, support is provided from Progress 9.1D onward.
4GL/ABL Database Access:
Client Server
12.x 12.x, 11.x
11.x 11.x, 10.x
10.x 10.x, 9.1x/3.1x
- Features introduced in the OpenEdge 12.x release cycle that affect the connection cannot be used when connecting to a Progress 11.x database.
- Features introduced in the OpenEdge 11.x release cycle that affect the connection cannot be used when connecting to a Progress 10.x database.
- Features introduced in the OpenEdge 10.x release cycle that affect the connection cannot be used when connecting to a Progress 9.1x database.
SQL-92 Database Access:
Clients for the SQL-92 Database access:
- SQL-92 ODBC Client
- SQL-92 JDBC Client
Client Server
12.x 12.x, 11.x
11.x 12.x, 11.x, 10.2x, 10.1x
10.2x 11.x, 10.2x, 10.1x
10.1x 11.x, 10.2x, 10.1x
10.0x 10.0x
9.1x 9.1x, 9.0x
SQL-92 Clients include ODBC, JDBC and ESQL/C, so since SQL-92 connections are always established as Client-Server connections, Progress Client-Server version connectivity rules apply:
- If both the Client and the Server are of the same Major releases, Client can connect.
SQL Exceptions to the Rule :
Starting in OpenEdge 10.1A, Type 4/wire protocol drivers were introduced. Because of this change OpenEdge 10.1x, 10.2x Drivers are not backwards compatible with OpenEdge 10.0x or 9.1x. OpenEdge 10.1x (type 4/wire protocol drivers) and forward, the drivers are both backward/forward compatible. So due to major changes in the connection protocol, an OpenEdge 10.x SQL-92 client cannot connect to a Progress 9.x database, and vice versa. When connecting to a Progress 9.x database via ODBC, use one of the following drivers:
MERANT 3.60 32-BIT Progress SQL-92
DataDirect 4.1 32-Bit Progress SQL92
Due to feature changes in the Drivers, Progress always recommends to use the Driver supplied with the license installed.
PASOE, AppServer, and NameServer:
Clients for the AppServer
- ABL Client (including WebClient)
- Java Open Client
- WebSpeed Transaction Server
- WebSpeed Agent
- AppServer Agent
- Web Services Adapter
- REST Adapter
- OpenEdge Adapter for Sonic ESB
- ActiveX / .NET Open Client
The NameServer follows the same compatibility rules as the Server listed below.
Client Server
12.x 12.x, 11.x
11.x 12.x, 11.x, 10.2A03, 10.2B
10.2A03, 10.2B 11.x, 10.x, 9.1x/3.1x
10.2A, 10.1x, 10.0x 10.x, 9.1x/3.1x
9.1x/3.1x 9.1x/3.1x, 10.x
The general Rule of Thumb regarding Client/AppServer connectivity is 1 major release difference.
When connecting to a previous version Server, the connection will work provided that only the previous version functionality is used.
For example:
Features introduced in the OpenEdge 10.x release cycle that affect the connection or that are propagated between client and server cannot be used when connecting a Progress 9.1x component to an OpenEdge 10.x AppServer or vice versa.
A 10.1A WebSpeed Transaction Server will work with a 10.0B, 10.0A, 9.1E NameServer, as long as the new functionality of the 10.1A NameServer is not attempted with the earlier version NameServer.
Microsoft will no longer support its JVM as of September 30, 2004
- ActiveX Open Client is neither available nor supported in OpenEdge 10
- ActiveX Client application will need to be migrated to .NET Framework
WebSpeed Transaction Server (WebSpeed broker):
Clients for the WebSpeed Transaction Server
Client Server
11.x 11.x, 10.2A03, 10.2B
10.2A03, 10.2B 11.x, 10.x, 9.1x/3.1x
10.2A, 10.1x, 10.0x 10.x, 9.1x/3.1x
9.1x/3.1x 9.1x/3.1x
The general Rule of Thumb regarding Client/AppServer connectivity is 1 major release difference.
When connecting to a previous version Server, the connection will work provided that only the previous version functionality is used.
As there is no OpenEdge 12.x classic Webspeed messenger or Webspeed Transaction Server available (deprecated in OpenEdge 12.x) there is no compatibility line for a 12.x webspeed messenger client in the compatibility list above.
For example:
Features introduced in the OpenEdge 10.0x release cycle that affect the connection or that are propagated between client and server cannot be used when connecting a Progress 9.1x component to an OpenEdge 10.x WebSpeed Transaction Server or vice versa.
Dataserver Broker:
If using the DataServer brokering technology for N-Tier deployment, the OpenEdge versions of the client and the DataServer broker must be at the same maintenance level.
For example, an OpenEdge 11.5 client cannot connect to an OpenEdge 11.4 DataServer Broker. Similarly, an OpenEdge 11.4 client cannot connect to an OpenEdge 11.5 DataServer Broker.
Administration of Server products:
Administration (or management) is associated with the server component itself and therefore must be the same version.
- Administration tools associated with the Server product (including Progress Explorer (retired), OpenEdge Explorer, OpenEdge Management, Database Administration, Dictionary, Compiler) must be the same version, including Service Pack/LTS Update level (and Hotfix if applicable) as the Server Version.
Otherwise errors such as the following will be returned:
Database <dbname> is a R## database. This dictionary cannot be used with a OpenEdge R## database. Use the dictionary under OpenEdge R## to access this database.
There are no R12 databases connected. This tool cannot be used with a OpenEdge R11 database. Use the tool under OpenEdge R11 to access such a database.
When porting across major versions r-code must be recompiled, further information is provided in Articles:
