OpenEdge Data Management: DataServer for Microsoft SQL Server

Record creation
Suppose that you have a table called customer with a field called custnum that is
defined as an indexed field, and you write the following procedure:
DO TRANSACTION:
CREATE customer.
ASSIGN
customer.name = "SMITH"
customer.custnum = 10
customer.address = "1 Main St".
END.
When you run this procedure:
• The OpenEdge database does not create the record at the CREATE statement.
Instead, it writes it to the database at the end of the record scope or when the
index information is supplied, whichever occurs first. In this example, the
OpenEdge database writes the record after executing the statement custnum =
10.
• The DataServer writes the record later, at the end of the record scope. In this
example, it writes the record after executing the statement END.
The following procedure, which uses multiple buffers for the same record, illustrates the
differences between the OpenEdge database and DataServer record creation:
DEFINE BUFFER xcust FOR customer.
CREATE customer.
customer.custnum = 111.
FIND xcust WHERE xcust.custnum EQ 111.
DISPLAY xcust.
In this procedure, the code creates a customer, sets custnum equal to 111, then finds
and displays the customer record using custnum (the unique index). In this case:
• The OpenEdge database displays the customer 111 record.
• The DataServer fails to find customer 111 because it has not yet written the record
for customer 111 to the data source.
To get a consistent response from the DataServer, use this procedure instead:
DEFINE BUFFER xcust FOR customer.
CREATE customer.
customer.custnum = 111.
VALIDATE customer. /* or RELEASE customer. */
FIND xcust WHERE xcust.custnum EQ 111.
DISPLAY xcust.
OpenEdge Data Management: DataServer for Microsoft SQL Server 91