Mike Ruskai Guest
|
Posted: Thu Nov 30, 2006 12:43 am Post subject: "Corrupt" Paradox tables when using secondary index |
|
|
I have a 170MB table with a 16K block size, and 230K+ records. This
is only an example table, however, since it can be reproduced with 20
other tables that vary in size, but not definition.
The problem is that using a secondary index to determine display order
in a BCB app (TDataGrid via TTable) causes the infamous "Corrupt file
- other than header." error message.
Let me be clear at this point that the table is manifestly not
corrupt. This is a spurious error.
The secondary index is compound, where three fields will always
contain data, and one (a string field) may be empty or NULL.
If I recreate the index using only three fields (leaving out the one
that can be empty), the problem does not appear.
This is not an ideal workaround, of course, because the records may be
out of order.
Is this a known bug, and are there any more correct workarounds (i.e.
that allow a complete secondary index with empty values)?
--
- Mike
Ignore the Python in me to send e-mail. |
|