Textual data code design

Application displays, printer file specifications, and user-created commands typically contain a large amount of constant text. Application displays, printer file specifications, and user-created commands also contain input and output fields such as headings, field prompts, instruction lines, and function key descriptions.

You can use different techniques to specify, store, and use constant text. You can use each technique for specific types of textual data components. Each technique has its advantages and disadvantages.

• Early message binding
  Text can be stored externally from the source code in a separate message file but is bound into the object when it is created.
• Late message binding
  Text can be stored externally from the DDS source code in a message description and is bound only to the display format at run time.
• Direct coding as an unnamed output field
  The most common way to define constant text is to specify the text directly in the source code as a literal. While this method is the most common way to define constant text, it is the most difficult to translate. Avoid using this method whenever coding an application, even if the application is not planned for translation.
• Text stored in database files
  Text can be stored externally from the source code in a database file, retrieved by the application program, and then moved to the display or print format at run time.