- James Hsu
- PowerBuilder
- Wednesday, 4 November 2020 12:06 AM UTC
We are currently working on migrating an application developed in PB 11.5 to PB 2019 R2. For about 80% of the functionalities the migration went fine, but for the 20% where we use the datawindow to update the database gives us the following error when inserting into a datetime2 column:
SQLSTATE: 22008 [Microsoft][ODBC Driver 11 for SQL Server] Datetime field overflow. Fractional second precision exceeds the scale specified in the parameter binding.
I know that PB is not compatible with datetime2 data type in MSSQL, but we do not want to change all of our datetime2 columns to datetime. I saw a suggestion for casting datetime2 into a string for PB app to use and pass it into a stored procedure where it would handle the passed in string and insert into datetime2 column natively. However, this insert is a part of a transaction involving updates to multiple tables and with this method rollback from PB would not work. What do people typically do to get around this limitation?
Sincerely,
James
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.