Working with non OpenEdge Databases

Description
How to use it
Settings/Attributes

Description

Some customers may have database technologies other than Progress OpenEdge (e.g. MySQL). When working with them, there are a few things to check and possibly change from the default configuration.

One important point is the missing Build.One GUID: selfhdl when working with non-OE databases. The selfHdl is an internal ID that is required for some standard functionality such as Global search (OmniSearch) and can be easily added to OE databases, but currently not to non-OE databases.

How to use it

The default link between search and detail screens is also done with the selfHdl. To change this you will need to change this value in the following places:

In the Column of the grid from which you link: Go to the specific column and change the attribute KeyField to the foreignKey of the database table
In the DSO of the target detail page: Change the attribute KeyFields to the foreignKey(s) of the database table

Settings/Attributes

KeyField	Attribute of the Column in a Grid	selfhdl, recordid
Attribute	Description	Example/Values
KeyFields	Attribute of the DSO	selfhdl, recordid

Back to Documentation

Back to Home Page