Following up on Miguel's statement:

If you are updating with a DW, please ensure that the ROWS / UPDATE PROPRTIES window shows that the datetime field is selected to be updated.

I suggest testing out the new OLE DB driver for SQL Server that is in PB 2019 R3 and see if that solves your issue.  Beta version of PB 2019 R3 is currently available, and there is a good webinar about this new driver.

MSSQL uses 7 decimals on DateTime2 while PowerBuilder's precision is 6 decimals if I'm not mistaking.
You may have those 10-millionth's fractional mismatch.

If you set DisableBind=1 and capture SQL statements in SQLPreview event (DW,DS, or transaction) you can capture the "failing" SQL. Those are excellent test cases in MS SQL Mgmt Studio to see what actually happens.

@@ROWCOUNT should tell you same value as PB transaction's SQLNRows. When SQLNRows = 0 for UPDATE from DW you will see error = row changed between retrieve and update.

HTH /Michael

Hi,

1) Are you doing an embedded UPDATE ... SET .... statement or an Update() on a datawindow or datastore?

2) Do you get any error message?

3) Can you make a small test table with a field which you do define as datetime2?

4) If it works with datetime2, than maybe you won't have to set the compatibility mode. (since you said it worked for a normal datetime, when using that).