Connectivity rules between clients and servers are as follows:
Client products can connect to server products of the same release number and one major release backward.
For example, OpenEdge Release 11 clients can connect to both OpenEdge Release 11 and Release 10 Application and Database Servers.
Client products can connect to AppServer products of one major release backward and one major release forward.
For example OpenEdge Release 10 clients can connect to OpenEdge Release 11 Application Servers.
Clients prior to OE10.2A03 and OE10.2B01 are implemented using the Progress V9 Application Server protocol, and appear to be Progress V9 Clients from a system perspective. Consequently these clients cannot interact with an OpenEdge Release 11 Application Server.
OpenEdge Release 10.2A clients must be at Release10.2A03 or later, and OpenEdge Release 10.2B clients must be at Release 10.2B01 or later in order to connect to an OpenEdge Release 11 Application Server.
Server products, when connecting to another server, behave like a client, and follow the client rules stated previously.
Client to client compatibility is not applicable.
Shared memory connections between clients and server require the release numbers to match exactly.
Database migration/conversion is not required because there is no internal database major-version change this release.
R-code compilation is not required because there is no r-code major-version change in 11.6. An OpenEdge Release 11.6 client can execute r-code generated with 11.0. However an OpenEdge Release 11.6 client can not execute r-code generated with release 10, 9, or earlier.
Note: An OpenEdge Release 11.1 client can execute r-code generated with 11.6. You must recompile the r-code generated with 11.6.
R-code is portable across all platforms of the same user interface type.
Client products can connect to server products of the same release number and one major release backward.