---

 Comments

---

The problem was caused by the SAVE UPDATES functionality not detecting updates by other sessions, and wasn't seen in the past because most of the time the SAVE UPDATES statements are being called from within a job, not a session that is kept open and also used for other update activities.

The conditions for this problem to occur within the same session are:

1) The table that is being updated must be open and must stay open through all of these of steps.
2) The SAVE UPDATES statement must be run.
3) The table that is being updated must be updated by another session.
4) The SAVE UPDATES statement must again be run. During this step, the SAVE UPDATES will miss the updates occurring in step 3).

---

 Resolution

---

Fixed Problem on 4/5/2016 in version 2.23 build 2

---

 Products Affected

---

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial