Databases that are only pulled from the native environment or are migrated without the
CREATE RECID FIELD option must either choose a unique index key from each table or the native
ROWID to represent the
PROGRESS_RECID to support the
RECID and
ROWID functions, and forward and backward scrolling within their ABL sessions. OpenEdge will internally map the selected unique key or native
ROWID to the
PROGRESS_RECID and
ROWID functions. It is important to note that the unique index key used to derive the OpenEdge
ROWID must be a single component index for it to map to the
ROWID of a temp-table as described in the following discussion. For more details, see the
ROWID function discussion in
InitialProgramming Considerations.
Also, before discussing
ROWID as it relates to the
RUN STORED-PROC statement, it is important to understand an important property of the OpenEdge
ROWID. See
ROWID: Standard ABL behavior for more information.