1. Charlie Cummins
  2. PowerBuilder
  3. Tuesday, 14 April 2020 22:13 PM UTC

Hi everyone,

We are migrating Windows 10 PB 2017 R3 Applications with a heavy stored procedure back-end from ASE and to MS SQL Server 2017.  BTW, I already put an advice issue out for the optimum database driver to use, thanks everyone for their help on that issue.  

But I did want to understand what I am doing wrong in setting up the PBNewSPInvocation in the PB Database Profile Setup for MS SQL Server 2017 using ODBC.  I do have a working ODBC database connection to our MS SQL Server 2017 database and can run inline-SQL and stored procs with no-parameters. 

When I add a stored proc with a output variable I get a compiler error on my stored procedure declare in the PowerBuilder editor.  Here is the error "Database C0038: SQLSTATE = 37000[Microsoft][QDBC SQL Server Driver][SQL Server]Cannot use the OUTPUT option when passing a constant to a stored procedure."  Here is the declare statement "DECLARE DBGET_GRPNAME PROCEDURE FOR pb_get_dbuser_name_out  @int_out_return = :ll_rv OUTPUT USING THIS;"  It seems like it doesn't like the "@" sign.  This compiles fine under ADO.NET.

For starters I just wanted to make sure I had the PB Database Profile Setup correct for the database parameter PBNewSPInvocation.  The ODBC PB Database Profile Connection is setup off the defaults except StripParmNames='Yes', CallEscape='No' and the Driver-Specific Parameters field.  In that field I have the value "PBNewSPInvocation=YES" without the quotes.

It seems like this is not correct because of the compiler errors I am getting, maybe there is another adjustment to setup that needs to be made?

Thanks for your help.

 

 

 

 



There are no replies made for this question yet.
However, you are not allowed to reply to this question.