Icon View Incident Report

Serious Serious
Reported By: Deven Hickingbotham
Reported On: 12/8/2000
For: Version 2.05 Build 1
# 680 Adding a Primary Index Via AddIndex Instead of CreateTable Will Cause a #8961 Header Corrupt Error

My DBISAM code has until now assumed that a newly created table required a primary index as required under 1.xx. I tried changing my code to treat DBISAM 2.x just like 'other' tables where the driver populates an unindexed table, then adds the indexes. Here is the rough sequence:

1. create the table
2. set exclusive
3. open
4. populate the table
5. add the index(es)
6. close
7. unset exclusive
8. open, causes error 8961, corrupt header

This sequence works if step #1includes defining the primary index.

Resolution Resolution
Fixed Problem on 12/12/2000 in version 2.06 build 1