Progress/400
Product Guide


Naming Conventions

One factor to consider when designing for consistency between Progress and DB2/400 is the kind of restrictions each has for naming tables or files and fields. Progress/400 handles the conflicts in naming conventions for you.

Object Names

These are the restrictions for naming Progress and DB2/400 database objects, including files, tables, fields, and indexes:

NOTE: The prefix, P__, is reserved for files in the Progress/400 server schema.

The set of characters that Progress allows includes all of the characters DB2/400 allows, so no modifications to the DB2/400 file or field names need to be done before a Progress application can reference them. However, when you move a Progress database to the AS/400, Progress/400 modifies Progress names as necessary according to these rules:

For example, the property sheet for a field named sales-representative shows the AS/400 name to be SALES_REPR.

Unique Table and File Names

Progress requires that a table name be unique within a database. DB2/400 requires that a filename be unique within a library. Because you can include database files from multiple libraries in a single Progress/400 dictionary library, you might have duplicate names.

Progress/400 resolves nonunique table names for you when creating or modifying the server schema. For example, it might remove underscores and embedded vowels, and append underscores (_). The properties sheet in the Progress/400 Data Dictionary shows you which DB2/400 file mapped to a table in the schema. When you create files using the Progress/400 Data Dictionary, you must enter unique Progress names.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095