OpenEdge Data Management: DataServer for Microsoft SQL Server

Interfacing with RDBMS stored procedures
The easiest way to create a buffer that accepts data from stored procedures is to use the text of
the SQL SELECT statement from the stored procedure. This ensures that you define your data
types correctly and in the correct order. Use a native process such as sp_helptext to view the
stored procedure from a MS SQL Server, or view procedures in the system tables.
The examples in this section do not use the supplied proc-text-buffer buffer. Instead, they
show how to define formatted buffers by creating views in the data source, using the following
syntax:
Syntax
CREATE VIEW _BUFFER_buffer-name
Example 3–8 and Example 3–9 show the views created in your MS SQL Server data source that
you can use as buffers to store the results from the stored procedure pcust.
CREATE VIEW _BUFFER_pcust_orders AS SELECT customer.cust_num,
customer.name, order_num FROM customer, order_ WHERE 1 = 0
GO
Example 3–8: First view created in your MS SQL Server data source
CREATE VIEW _BUFFER_pcust_states AS SELECT cust_num, state.state
FROM customer, state WHERE 1 = 0
GO
Example 3–9: Second view created in your MS SQL Server data source
Example 3–10 shows ABL procedure results of the previous stored procedure pcust as it is
written into the new buffers pcust_orders and pcust_states.
/* Results of the first two example code examples - Typed buffers */
RUN STORED-PROC pcust (20, output 0, output 0).
FOR EACH pcust_orders:
DISPLAY pcust_orders.
END.
FOR EACH pcust_states:
DISPLAY pcust_states.
END.
CLOSE STORED-PROC pcust.
DISPLAY pcust.orders pcust.states.
Example 3–10: Result set of pcust - typed buffers
Because two different buffers have been defined, the returned values maintain their data types
instead of being converted to character strings and stored in the OpenEdge-defined buffer
proc–text–buffer. You can then use the returned values in calculations without first
converting them back to their original data types. In addition, the two separate buffers make
your output look cleaner, allowing ABL to build a new default frame for the two different types
of output. Reading your results into an explicitly defined buffer also allows you to manipulate
the data just as you would manipulate data from an OpenEdge database; for example, with
Frame phrases and FORM statements.
3–19