Progress
Portability Guide
Introduction
The DataServers for ORACLE, DB2/400, and ODBC let you work within the Progress Application Development Environment (ADE) while accessing your non-Progress databases. In addition, the DataServers are compatible with other Progress database features and Progress extensions. Some of these features are:
- Data Dictionary — You use the Data Dictionary to modify database schemas, create indexes, and define database triggers, validation expressions, and help messages.
- Application Builder (AppBuilder) — You use the AppBuilder to design and generate code for your graphical interfaces.
- Progress programming model — You use this programming model to develop applications that respond to choices that your end users make.
- Database triggers — You use database triggers to define a block of Progress 4GL code that executes whenever a specific database event occurs, such as creating a record, deleting a record, or assigning a value to a field.
If you want your applications to use these features, you must make minor modifications to your non-Progress tables. The following sections describe these modifications. For a more detailed information on modifying non-Progress tables, see the appropriate Progress DataServer Guide .
The Progress DataServer Guides describe how to use the DataServers to access non-Progress databases. They tell how to build DataServer modules and how to program applications that access Progress and non-Progress database management systems. They also provide tutorials. Each DataServer has its own guide—for example, the Progress DataServer for ORACLE Guide, the Progress/400 Product Guide, and the Progress DataServer for ODBC Guide. These guides also include portability solutions specific to each DataServer.
The Progress Database Design Guide introduces the fundamental principles of relational database design using a sample database and the Progress Data Dictionary. As the Progress Database Design Guide stresses, designing a database is an iterative process. It consists of gathering the information and processing requirements of your business, and developing and refining a corresponding database structure. This chapter, by contrast, focuses on issues to keep in mind as you design an application for portability across database systems.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |