Examples of portable and nonportable r-code
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Not all r-code is portable. You can usually port r-code between clients as long as you do not change display architectures, database types, platform classes or major r-code versions. For example:
- If you port a Windows application to character-mode, you must recompile, because the display architecture has changed.
- If you port a character application compiled against an ORACLE DataServer on a Linux workstation to a character application accessing an ORACLE DataServer on a Microsoft Windows workstation, you do not have to recompile (assuming that the ORACLE release level does not change and both platforms are 32-bit or 64-bit, respectively).
- If you port a character application compiled against the DataServer for ORACLE on a Linux workstation to a character application accessing the DataServer for Microsoft SQL Server on an Microsoft Windows workstation, you must recompile because the database type has changed.
- If you migrate an application from one major OpenEdge release to another you must recompile it. You can upgrade directly to the latest release without upgrading to each intermediate version.