OpenEdge Data Management: DataServer for Microsoft SQL Server

ROWID Support
It is important to note that the unique index key used to derive the Progress 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 Chapter 2, “Initial
Programming Considerations.”
Starting in OpenEdge Release 10.1B, the default external representation of ROWID enables the
MS SQL Server DataServer to use a 64-bit integer value for ROWID.
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. The “ROWID—Standard ABL
behavior” section on page 3–33 presents this information.
ROWID—Standard ABL behavior
The ROWID value of a temp-table buffer will be different than the ROWID value of a record
BUFFER even if the underlying data is identical. This difference exists because the ROWID
function relies on the record buffer name. Example 3–24 shows the standard, expected ABL
behavior.
DEFINE VARIABLE rid-1 AS ROWID NO-UNDO.
DEFINE VARIABLE rid-2 AS ROWID NO-UNDO.
DEFINE VARIABLE ttHandle AS HANDLE NO-UNDO EXTENT 1.
t
DEFINE TEMP-TABLE ttCustomer LIKE Sports2000.Customer
FIELD tRecid AS INTEGER
FIELD tRECID_ident AS INTEGER.
ttHandle[1] = TEMP-TABLE ttCustomer:HANDLE.
FIND FIRST Customer WHERE Customer.CustNum = 1 NO-LOCK.
rid-1 = ROWID(Customer).
RUN STORED-PROC send-sql-statement
LOAD-RESULT-INTO ttHandle (“select * from customer where custnum = 1”).
rid-2 = ROWID(ttCustomer).
IF rid-1 NE rid-2 THEN
MESSAGE “The same record but different ROWID’s”.
Example 3–24: Expected ABL behavior—ROWID value of a temp-table buffer
The following sections illustrate the differences between the ROWID value of a temp-table buffer
and the ROWID value of a record BUFFER so that you can best understand, program for, and
leverage the use of the ROWID function with the LOAD-RESULT-INTO clause of the RUN
STORED-PROCEDURE command.
3–33