---

 Comments

---

The issue was due to a change in 2.15 and higher to fix the problem reported in incident report #3955. The change was to allow computed columns to save their values to output streams. However, computed columns still completely ignored any incoming values in input streams, and this created an asymmetrical situation where computed columns would be saved in replication streams stored in update files, but any attempt to load such update files would fail because the computed columns were not properly advancing the stream position past the incoming computed column values.

If you encounter this issue, then please make sure to update all involved ElevateDB installations to 2.17 or higher, and then re-attempt the loading of the updates.

---

 Resolution

---

Fixed Problem on 5/12/2014 in version 2.17 build 1

---

 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