Ok, I think that I found the issue. I did not apply any more changes to the DB Profile. Our app is over 15 years old and many hands at varying times have made modifications. I was working on a workaround to our DBPARAMBIND problem by modifying the Stored Procedure and what parameters it expected (limiting datetime parameters), but the code was not "pulling in" or recognizing the latest changes I made. It turns out that the following style of code to invoke a Stored Procedure was not pulling in the most recent version of the SP:
SQLCA.PROCEDURE_NAME(ld_param1, ld_param2, ldt_param3...)
I am not sure what version of Stored Procedure it was invoking?? Only then did I attempt to rewrite the call to what I was familiar with in the following format:
Declare pb_procedure_alias procedure for PROCEDURE_NAME &
@param1 = ld_param1,
@param2 = ld_param2,
@param3 = ld_param3 USING SQLCA;
Execute pb_procedure_alias;
The DBPARAMBINDINFO error disappeared. Original problem solved, no need for a workaround.
Not sure if this issue is a result of our move to SQL Server 2008 and then to 2012 and still using an older version of Powerbuilder (12.1 Build 7000)???
Explanations???