Re: Corrupt Indexes

[mjs]

I have had the same thing happen, it appears to be a corrupt table.  I fixed it and saved the data by projecting a new table from the old table, deleting the old table and projecting the orginal table from the new table.  That is... PROJECT newtable FROM oldtable USING ALL DROP TABLE oldtable PROJECT oldtable FROM newtable USING ALL --make sure the oldtable is ok, and if it is..... DROP TABLE newtable. --then go recreate your indexes in the ususal fashion.   Hope this helps Mike Sinclair   William Mason wrote: Hoping for help and providing a warning: We have begun to encounter REPEATED index corruptions, resulting in a scenario in which rows seem to both exist and not exist at the same time.  The usual tell-tale clue is if one were to compare the row counts returned by the LIST TABLE and SELECT COUNT(*) FROM they are different.  And the data is NOT retrievable. The only common link seems, at this time, to be that the tables in question have UNIQUE indexes declared.  We have begun to remove these indexes in an effort to contain this problem.  Maybe a bit late, as it has already cost us substantial amount of money due to invoices not being calculated correctly because the details of the charges got "lost". Has anyone else experienced such behavior?  Is this a noted issue?  This issue has moved from table to table, so I am not considering it a coding issue, and I have way too many projects to debug index issues, so any help would be appreciated. Windows 2000 & NT 4.0; RBWin 6.5++ Also, this behavior has happened on databases that do not share hardware, so I have discounted the possibility of NIC or other hardware failures.  William Mason