OpenEdge Data Management: DataServer for Microsoft SQL Server

Record creation
The VALIDATE or RELEASE statement causes the DataServer to write the customer 111 record to
the database before the FIND statement occurs. Using the VALIDATE or RELEASE statements
forces a write to the data source even if the transaction has not yet completed. This makes the
record available in the local database cache and it will be found if the record must be re-read
before the end of the transaction.
Note: If you set the default value when creating a record, you must change the value before
you create another record with the default value if the field is part of a unique key.
Otherwise, the second record will cause a duplicate key error.
Record updates are handled similarly to record creation. A record is updated in a MS SQL
Server data source at the end of record scope or at the end of a transaction, whichever comes
first. For example, when you run the following procedure, the newly updated record is not
found:
FIND customer WHERE customer.custnum EQ 12.
DO TRANSACTION.
ASSIGN customer.address = "14 Oak Park".
FIND customer WHERE customer.address EQ "14 Oak Park".
END.
To send the record to the data source sooner, use the VALIDATE statement, as follows:
FIND customer WHERE customer.custnum EQ 12.
DO TRANSACTION:
ASSIGN customer.address = "14 Oak Park".
VALIDATE customer.
FIND customer WHERE customer.address EQ "14 Oak Park".
END.
For more information about record scoping and transaction behavior, see OpenEdge Getting
Started: ABL Essentials.
2–35