It was the update properties.  Thank you for steering me in the right direction!  Truly appreciate it!

Anna

Hi Anna;

   There should be no difference in the Update() command logic internally of how the DWO handles the DML for the changed column(s). The first thing that I would check is that the DWO in 12.5 and the DWO in PB2019R3 have the same Update Properties and Updatable Columns set. I would check that first. Any variance here could explain the different behaviour

   The other check could be to use the SQLPreview event on the DC/DS to see if the SQL generated in v12.5 is the same update SQL that you see generated in PB2019R3.

   Alternatively instead of the SQL Preview event, you could set an SQL Trace in the V12.5 and v2019R3 of the App and then see what is being updated in each version of the App. For example:

• SQLCA.DBMS = "XXX"              // OLD
• SQLCA.DBMS = "TRACE XXX"   // NEW

   You can also run the DWO in the DW Painter and in the "Preview" pane emulate the Retrieved and Updated data and then see if the "save Changes" on the DW Painter's toolbar works without error.

   Other considerations could also be newer / different DBMS, DB Client, DB Access method, etc between the V12.5 ans v2019R3 Apps.

HTH

Regards ... Chris