Unfortunately there is no logic or algorithm that allows one to identify the version of the r-code and relate it to the Progress version using the version number displayed in this error message. Typically the actual number is unimportant. The only time it really isn't is if you no longer have the ability to compile (i.e. local licensing issue or loss of source code).
The first number in the error is embedded in the r-code when complied and the second represents the version associated with the client that is running the code.
If you are receiving the error, you can compile code in the suspected version and run on the problem version. If you need to know what version the r-code version number corresponds to contact Progress Technical Support for assistance.
Below are the values of r-code version related to Progress / OpenEdge version.
| R-Code Version | Progress / OpenEdge Version |
|---|
| 900 | 9.0x (has appserver code) |
| 908 | 9.0b (without acs segments) |
| 909 | 9.0b (uses 4 acs segments) |
| 1005 | 10.0a |
| 1006 | 10.1b |
| 1007 | 10.1a (with new datasets/64bit) |
| 1008 | 10.2b (with 64bit) |
| 1009 | 10.2b (support for stream handles) |
| 1100 | OpenEdge version 11.x |
| 1200 | OpenEdge 12.x |
For values significantly higher than the above version numbers (which in some versions of OpenEdge 10 indicated 64-bit r-code) take the number listed and subtract 16384 to get the adjusted r-code version.
Example:
R-CODE version in error is 17391.
17391 - 16384 = 1007
