-
D Aggelis
- PowerBuilder
- Friday, 11 September 2026 12:32 PM UTC
Hi,
After migrating to 2025 R2, we have strange error in some datawindows when updating a field that triggers actions in the underlying update trigger. The trigger affects rows on other tables not included in datawindow's sql.

Database is SQL 2022 and the connection string is
SQLCA.DBMS = "MSOLEDBSQL SQL Server"
SQLCA.ServerName = "atlas"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Database='elin_2040',ArithAbort=1,OJSyntax='ANSI_Escape',Provider='MSOLEDBSQL19',TrustedConnection=1"
This is from the trace:
(14331188): PREPARE:
(14331188): UPDATE cehmkim SET flag_enhm = 'Ο' WHERE machine_id = 'ath' AND proel = 'cl' AND key_id = 390126597 AND flag_enhm = '*' (DBI_PREPARE) (604.193 MS / 2905.250 MS)
(14331188): EXECUTE:(DBI_DW_EXECUTE) (0.002 MS / 2905.252 MS)
(14331188): GET AFFECTED ROWS:(DBI_GET_AFFECTED_ROWS) (0.002 MS / 2905.254 MS)
(14331188): ^ 0 Rows Affected
(14331188): CANCEL:(DBI_CANCEL) (0.062 MS / 2905.316 MS)
(14331188): ROLLBACK:(DBI_ROLLBACK) (9.938 MS / 2915.254 MS)
In PB2022 and connection string
SQLCA.DBMS = "TRACE ADO.Net"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Namespace='System.Data.OleDb',Provider='SQLOLEDB',DataSource='atlas',Database='elin_2040',TrustedConnection=1"
doing exactly the same update we have no problem. As you can see from the trace the number of rows affected is reported.
(06951028): PREPARE:
(06951028): UPDATE cehmkim SET flag_enhm = 'Ο' WHERE machine_id = 'ath' AND proel = 'cl' AND key_id = 390126597 AND flag_enhm = '*' (41.628 MS / 378.219 MS)
(06951028): EXECUTE: (0.000 MS / 378.219 MS)
(06951028): GET AFFECTED ROWS: (0.000 MS / 378.219 MS)
(06951028): ^ 15 Rows Affected
(06951028): COMMIT: (8.647 MS / 386.866 MS)
As a workaround we found out that
EXECUTE IMMEDIATE "SET NOCOUNT ON" USING SQLCA;
after SQLCA.of_connect() solves the problem.
Is this a correct solution? We are afraid moving it to production because we don't know if there are side effects behind this.
Any ideas?
Regards
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.