DBParm: PBNewSPInvocation
\The Sandbox \PB History & Future \New In PB 9 \New In PB 9.0.1 \DBParm: PBNew SPInvocation
XP Look & Feel
PBNI Support
for Any
PBXDraw
VisualObject
PBNI
Source Files
SetProxy
ServerOptions
Heap Manager
Included
Hiding the JSP
Page View
Menu Options
Select Painters
New Excel
Save Format
DBParm: PBNew
SPInvocation
Additional
9.0.1 Changes

The PBNewSPInvocation DBParm enables you to use the OUTPUT or OUT keywords when you invoke a stored procedure using the ODBC interface. The behavior of the PowerBuilder ODBC driver when this DBParm is set is consistent with the default behavior of the OLE DB and JDBC drivers.

The DBParm can be set dynamically at runtime after connecting to a database. You can also set it in your PBODB90.INI file if you want to create and retrieve data into a DataWindow with a stored procedure data source in the DataWindow painter. The DBParm has no effect when you use RPC to invoke a stored procedure.

When this DBParm is not set, output parameters might not be returned when you use an embedded SQL command to call a stored procedure. When PBNewSPInvocation is set to “Yes,” you can use a statement like the following to obtain the value of the stored procedure's output parameter:

    DECLARE sp_test PROCEDURE FOR SP1 VAR0=:ARGIN, VAR1=:ARGOUT OUTPUT USING SQLCA;

If the stored procedure contains result sets, you must fetch the result sets first. If the stored procedure has a return value and you want to obtain it, use the format RC = SP1:

    DECLARE sp_test PROCEDURE FOR RC=SP1 VAR0=:ARGIN, VAR1=:ARGOUT OUTPUT USING SQLCA;

When PBNewSPInvocation is set to “Yes,” the values of the PBUseProcOwner
and CallEscape DBParms are ignored.

PBL Peeper PB Help PB History
& Future About Us Feedback Site Map

Google
 
Web www.techno-kitten.com
www.sybase.com