-
Richard Hartman
- PowerBuilder
- Thursday, 11 December 2025 01:42 AM UTC
A while back I posted a question regarding mssql server and output params on stored procs not working properly.
That can be found here:
https://community.appeon.com/qna/q-a/mssql-server-stored-proc-out-params-causing-problems
I got called away from it for a while, so it went idle, which is why I started a new topic after marking the reply that solved it ... partially.
Anyway, one of the answers got me working ... for a toy situation, but my real proc is still malfunctioning. I am hoping someone can spot where I am going wrong here.
First the toy situation (which works):
MSSQL Server:
CREATE PROCEDURE dbo.t_whereami
@innum int,
@instr char(30),
@srvr char(30) OUTPUT,
@db char(30) OUTPUT,
@val int OUTPUT
AS
BEGIN
...
Powerbuilder:
string servername
string dbname
string dunsel
int checklen
int num
DECLARE getinfo PROCEDURE FOR dbo.t_whereami
@innum = :num,
@instr = :dunsel,
@srvr = :servername OUTPUT,
@db = :dbname OUTPUT,
@val = :checklen OUTPUT;
execute getinfo;
After the execute, the sqlca.sqlcode is 0, and I can do the fetch into the three variables.
This is the one that does not work.SQL Server:
CREATE PROCEDURE dbo.s_oid_control_u01
@entity_name char(40),
@quantity int,
@first_new_val int OUTPUT
AS
BEGIN
...
Powerbuilder:
int new_value
int qty
string entity
DECLARE get_oid_value PROCEDURE FOR s_oid_control_u01
@entity_name = :entity,
@quantity = :qty,
@first_new_val = :new_value output;
EXECUTE get_oid_value;
After this, sqlca.sqlcode is -1, so we don't even get to the fetch. The sqlerrtext is :
SQLSTATE = 42000
Microsoft OLE DB Driver for SQL Server
Cannot use the OUTPUT option when passing a constant to a stored procedure.
I can not see what the difference between the first case and the second one is. What am I missing?
If it is possible that the bodies of the procs matter, I can post them. But shouldn't just the params matter for this error?
Powerbuilder 2021 build 1509
MSSQL Server 16.0.4195.2
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.