Icon View Incident Report

Serious Serious
Reported By: Uli Becker
Reported On: 5/12/2009
For: Version 2.02 Build 12
# 2990 Altering an Existing Index Can Cause Either a Corrupted Index or an Index Page Buffer Error

I had again problems with a compound index. Here are the steps:

1. I created a new table
2. I created some indexes
3. I changed one index by adding a second field to it
4. I queried the table with a simple (select * from ... where...)
5. Result: null
6. I repaired the table
7. Result: 5 records as expected.


Comments Comments and Workarounds
The workaround is to drop the index and then create the new version of the index. The problem was specific to altering an index.


Resolution Resolution
Fixed Problem on 5/13/2009 in version 2.02 build 13


Products Affected 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

Image