---

 Comments

---

The problem was that the checksum calculation was incorrectly including the internal object ID in the calculation. Therefore, if two tables were identical in terms of structure, but had different internal object IDs because they were created in a different order in each database catalog, EDB would incorrectly think that they were different.

To "fix" the checksum, make sure that you're using 2.03 Build 17 or higher, and perform the following steps with each table that needs to be copied:

1) Alter the table and add a dummy INTEGER column to the table.
2) Alter the table again, and remove the dummy INTEGER column.

After completing these steps, EDB will have recalculated the checksum properly, and you will be able to move around the table files without getting an error.

Also, the error message has been changed a bit to reflect that the structure is the source of the problem, not an internal version number (old design).

---

 Resolution

---

Fixed Problem on 7/6/2010 in version 2.03 build 17

---

 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