---

 Comments and Workarounds

---

The problem was with a conflict between the transaction used on the same table in the AFTER DELETE trigger and the internal transaction used for the DELETE FROM statement. The result is that some of the deletions would be discarded and the result would be as if the deletions never occurred.

This incident was not completely fixed the first time it was reported for 2.02 B6 and indicated as fixed in 2.02 B7. There was an issue with the regression test used, and the issue has now been fixed in 2.02 B15.

---

 Resolution

---

Fixed Problem on 6/15/2009 in version 2.02 build 15

---

 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial