CyberEDB.DB.Execute('ALTER INDEX "PrimaryKey" ON "Contacts" (Name COLLATE "ANSI_CI" ASC)');
CyberEDB.DB.Execute('ALTER TABLE "Contacts" ALTER CONSTRAINT "PrimaryKey" AS PRIMARY KEY ("Name")'+'VERSION 1.04');

---

 Comments and Workarounds

---

ALTERing an index changes its type to a normal index, as opposed to a primary key, unique, or foreign key, index. This causes table opens to fail if you ALTER the index used by a primary key, because ElevateDB assumes that a primary key index always exists, and after the ALTER a primary key index doesn't exist anymore.

The workaround for this is to not, ever, alter system-generated indexes that are used for constraints.

Also, the DROP INDEX and RENAME INDEX statements also had a similar issue.

---

 Resolution

---

Fixed Problem on 8/21/2010 in version 2.04 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial