Increase bScale in DBPARAMBINDINFO Error in PB 12.1 Ver 7000

Question

Hello.  Can't seem to get around the below error in PB 12.1 Ver 7000 when calling a Stored Procedure from Powerscript and am passing Datetime values.  I have played around with the connection strings Date formatting, but no matter what I attempt, it still looks like the PB is passing MM/DD/YYYY HH:MM:SS when SQL Server 2012 is expectring YYYY-MM-DD HH:MM:SS.
Full error:
SQLSTATE = 22007
Microsoft SQL Server Native Client 11.0
The fractional part of the provided time value overflows the scale of the corresponding SQL Server parameter or column. Increase bScale in DBPARAMBINDINFO or column scale to correct this error.
I've tried to use providers of SQLOLEDB, SQLNCLI10 & SQLNCLI11
Connection Profile String (Connection works fine):
// Profile for SIngle Sign On....
SQLCA.DBMS = "OLE DB"
SQLCA.Lock = "RU"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PROVIDER='SQLNCLI11',DATASOURCE='DB-DNS-ENTRY',PBCatalogOwner='dbo',INTEGRATEDSECURITY='SSPI'"
In the above, I have also tried to specify the following, whcih also works, but the same result (notice the date parameters match what SQL Server should expect for Datetime data types...
// Profile
SQLCA.DBMS = "OLE DB"
SQLCA.LogPass = <**************>
SQLCA.LogId = "USERID"
SQLCA.Lock = "RU"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PROVIDER='SQLOLEDB',DATASOURCE='DB-DNS-ENTRY',PROVIDERSTRING='Database=DB-NAME',DateFormat='yyyy-mm-dd',DateTimeFormat='yyyy-mm-dd hh:mm:ss.fff',TimeFormat='hh:mm:ss.fff'"

Answer 1

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???