Progress
Portability Guide
Examples of Portable and Nonportable R-Code
Some r-code is portable, and some is not. 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.
Here are some examples:
- 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 SUN workstation to a character application accessing an ORACLE DataServer on a Hewlett-Packard (HP) workstation, you do not have to recompile (assuming that the ORACLE release level does not change).
- If you port a character application compiled against the DataServer for ORACLE on a SUN workstation to a character application accessing the DataServer for ODBC on an HP workstation, you must recompile, because the database type has changed.
- If you port an application from Version 9.0 to Version 9.1, you do not have to recompile. If you port the application from Version 8.1 to Version 9.0, you do have to recompile. If you port the application from Version 8.3 to Version 8.2, you may not have to recompile, but it is highly recommended that you do so.
For more information on r-code portability, see the "R-code Portability and DataServers" section in "Database Design," and the "R-code" section in Programming Considerations." For detailed information on r-code features and functions, see the “R-code Features and Functions” appendix in the Progress Programming Handbook.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |