Source DBISAM Table:

CREATE TABLE IF NOT EXISTS "literatur"
(
   "nr" INTEGER,
   "quelle" VARCHAR(200),
   "jahrgang1" VARCHAR(20),
   "jahrgang2" VARCHAR(20),
   "seiten" VARCHAR(20),
   "titel" VARCHAR(500),
   "autoren" VARCHAR(500),
   "schlagwoerter" VARCHAR(500),
PRIMARY KEY ("RecordID") COMPRESS NONE
LOCALE CODE 0
USER MAJOR VERSION 1
);

CREATE INDEX IF NOT EXISTS "nr" ON "literatur" ("nr");
CREATE INDEX IF NOT EXISTS "quelle" ON "literatur" ("quelle");
CREATE INDEX IF NOT EXISTS "jahrgang1" ON "literatur" ("jahrgang1");
CREATE INDEX IF NOT EXISTS "jahrgang2" ON "literatur" ("jahrgang2");
CREATE INDEX IF NOT EXISTS "seiten" ON "literatur" ("seiten");
CREATE INDEX IF NOT EXISTS "titel" ON "literatur" ("titel");
CREATE INDEX IF NOT EXISTS "autoren" ON "literatur" ("autoren");
CREATE INDEX IF NOT EXISTS "schlagwoerter" ON "literatur" ("schlagwoerter");

---

 Comments

---

It was an issue with the particularly-large indexes in that table and the built-in index compression. During a page split, the index manager wasn't splitting the page properly based upon the resultant size of the split page and the compression.

---

 Resolution

---

Fixed Problem on 6/25/2008 in version 2.01 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial