OpenEdge Data Management: DataServer for Microsoft SQL Server

find.p
/* This code accesses an OpenEdge database. */
FIND demo.customer WHERE demo.customer.custnum EQ 3.
FIND PREV demo.customer.
DISPLAY demo.customer.custnum
LABEL "PROGRESS DATABASE RESULT" WITH FRAME new-frame.
/* This code accesses a MS SQL Server data source.*/
FIND mssdemo.customer WHERE mssdemo.customer.custnum EQ 3.
FIND PREV mssdemo.customer.
DISPLAY mssdemo.customer.custnum
LABEL "MSS DATA SOURCE RESULT" WITH COL 29.
ABL issues
When you run find.p with an OpenEdge table and a MS SQL Server table, you get
the following results (assuming that the database has records for customer numbers 1
through 4):
OPENEDGE DATABASE RESULT
If the FIND PREV statement fails, the cursor remains located after customer.custnum 3
in the OpenEdge table, which was the last record scanned. In the data source table,
the cursor is positioned at custnum 2. Failed finds do not affect cursor position in data
source tables.
Compiling OpenEdge procedures
The COMPILE statement lets you compile ABL procedures and save the compilations to
disk. This speeds up your application execution time since the application does not
have to recompile it every time you want to run a procedure.
To compile procedures that access a MS SQL Server data source, start up an
OpenEdge session and connect to the schema holder using the schema holder’s
logical database name, then use the COMPILE statement. If you change the name of the
schema holder after you compile a procedure, you must connect to the renamed
schema holder and recompile the procedure. For more information, see the “COMPILE
Statement” reference entry in OpenEdge Development: ABL Reference.
Note: You do not have to connect to the MS SQL Server database to compile a
procedure. The schema holder contains all the information that the compiler
requires.
OpenEdge Data Management: DataServer for Microsoft SQL Server 115
2
MSS DATA SOURCE
RESULT
2