RE: Table Corruption

is the "corruption" just the indexes? is the table size more than 1/2 the max, for that block size?

query out the data to a temp table.. run tutility or chimney sweep on it.. export to ascii.. make a new table from scratch.. import the ascii.. run tutility or chimney sweep on it.. add the indexes, pack the table

literally, do it all from scratch

> Please confirm this statement
" is the table size more than 1/2 the max, for that block " <

32k blocks, table has a max size of 2 gig.. sec indexes become disfunctional if the table is over 1 gig.. this particular table is only 86 meg, so no issue

> I will work on your steps,  However I dont have Chimney Sweep,   but I might have the tutility. <

tutility is the built in repair tool.. CS catches some advanced stuff, sometimes, that tutility doesn't.. an actual Repair catches many things that Verify doesn't even see.. it's all art, not science, unfortunately

in this case, what are the actual symtoms and/or error messages in the app that become the source of the problem?

in this case, other than the stupid "low ascii" errors, what errors does Verify give you?

> However,  I don't see how this is any different than taking a virgin copy of the table and inserting the records,  which has been done. <

if there's a bad pointer in the file, or a bad block on the disk, the ascii export process will often be "cleaner" than simply adding the records from the bad table to the empty table

if there's a "bad block" error in Verify, or something similar, and it's' still there after you go thru all the hoops I suggested, now you'll know you're doing the same "rinse and repeat" that won't go away

yes, I've seen that happen.. recently, I had a table like that.. trial and error, narrowed it down to one block of data.. added a record that split the block, the error moved to the new block.. deleted the new record, packed the table, it moved back.. deleted the "offending record", the next record error'd out.. kids, don't try this at home :-)

a Short in a compound key can cause corrpution, in any block size.. but especially in 32k block