Modifying field-level information
Print
- Last Updated: January 17, 2024
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
Modifying field-level information
You can modify field-level information.
To modify information in the schema holder at the field level:
-
Access the Data Dictionary,
if it is not already showing. Choose Fields.
The following Fields list appears:

- Select a table from the Tables list.
- Select a field from the Fields list.
-
Choose the Field Properties button.
The following dialog box appears:

You can enter information at the field level, such as a validation expression or a validation message.
The Data Dictionary displays the standard MS SQL Server names for data types and not the native ODBC data source names. Using the Data Dictionary, you can make the following changes:
- Change the data type or the format in which OpenEdge displays
the data. For example, choose the MS SQL Server
decimaldata type, which in turn defaults to the OpenEdgeINTEGERdata type mapping. However, you can change thedecimalmapping to either the OpenEdgeINTEGERorINT64data type instead. (The previous Field Properties dialog box shows theDECIMALdata type with theINT64data type option selected.) For more information about optional settings for data types, see Data types and Data Type Details. - For
CHARACTERfields that are not indexed, you can change the case sensitivity.
Note: You cannot create fields or add mandatory or extent properties to them. - Change the data type or the format in which OpenEdge displays
the data. For example, choose the MS SQL Server
-
Choose DataServer to view the field
name and position as stored in the data source.
A dialog box similar to the following appears:

Note: You cannot change data source information using the Data Dictionary. For example, thetotal_paidfield is namedtotal_paidin the database. - Choose OK.
-
When you are done making changes, choose OK to
return to the Data Dictionary main window.
Note: You can override field-level validation expressions in your application by including the appropriate ABL statement.