Your application typically uses the default set of global constant values defined in the application. You can set up alternate values for the global constants. For example, you can define and use constants for all strings you use in an application. You can create one set for each language you want to use.

The default set of constant values is stored in the database. You can create alternate sets of constant values and store them in files. You can override the default constants by specifying the file name before running an application or creating an image of an application.

When a global constant file is specified before running the application or creating an image, the values in the constant file override the default values stored in the database. The values in the constants file are in effect until you clear the field, specify a different filename, or edit a different application.

You can specify a global constants file when you use the imageapp command or when you run the application image. You can also specify a global constants file within ABF, before choosing Go or Image from the menu.

To create an image with the specified constants file, select Image.

You can create a global constants file with your system editor, or copy the default global constant values (that you defined through the Edit Global Constants window) into a file.

Create and edit a file with the following format:

For example:

The file can also contain comments beginning with a # character. For more information about the global constants file format, see the SQL Reference Guide section on the PM file format.

You change the alternate set of global constant values by editing the constants file. You cannot edit the alternate set of values through the Edit Global Constants window. You can edit the file with your system editor, from your operating system or from within Vision.

When you edit or destroy a constant in one file, it does not affect the constants in another file, or the default values in the database.

Prior to the current release of ABF, specify alternate languages in the Edit Global Constants window. Multiple sets of language-dependent constants values were stored in the database. In this release, only one set of global constants values are stored in the database, and alternate sets are stored in separate files. If you have a previous release of the database that contains multiple language values, the values are retained in the catalogs.

To convert global constants to the new format, create a file of global constants from the default set, as described in Create an Alternate Global Constants File. ABF creates a file with the global constants values separated by language, as shown in the example below. The data type is provided as a comment. You can then copy each set of values into its own global constants file.