Symptom
- There is a difference in behavior in PowerBuilder 12.6 Classic and .NET when declaring and executing a stored procedure that has a literal value for an input argument.
- In PowerBuilder .NET, executing the following statements:
DECLARE p21_DeleteCycleCount_wrong PROCEDURE FOR p21_deletion
@delete_primary_table_name = 'TableNameArg',
@delete_row_stmt = :ls_Delete USING trans;
EXECUTE p21_DeleteCycleCount_wrong; - In the SQL Profiler:
- PowerBuilder 12.6 returns:
- RPC:Starting exec p21_deletion @delete_primary_table_name='DeleteStmt'
- RPC:Starting exec p21_deletion @delete_primary_table_name='DeleteStmt'
- In PowerBuilder Classic:
- SQL:BatchStarting execute p21_deletion @delete_primary_table_name ='TableNameArg' , @delete_row_stmt ='DeleteStmtArg'
- PowerBuilder 12.6 returns:
Read more...
Environment
- SAP PowerBuilder .NET 12.6
- Microsoft SQL Server 2014
Product
SAP PowerBuilder 12.6
Keywords
pb,powerbuilder,.net,literal,argument,ado.net,stored procedure,sp,cr802827,802827 , KBA , BC-SYB-PB , PowerBuilder , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview