I have 2 tables damaged in OpenInsight 3.1, one with Error FS107 and the other with Error SSP271, I tried to run them the LH Verify, but it doesn't fix the tables. If someone had any utility for repare them besides LH Verify please let me know, I would apreciete any help.

Thanks

Alonso Duarte

FS107: "Error unknown" - establish first that this table actually exists in the data volume. Get the REVnnnn number (Database manager, Utilities, OpenInsight tables, LH table info), and then using explorer or DOS see if the tables (ie. the REVnnnn.LK and REVnnnn.OV) are there. Check their sizes - the .LK file cannot be 0, the .OV file can. If all is well, do the same for the index files if your table has indexes on it.

SSP271: "The header of table %1% is corrupted for fix" - prevents you from fixing the table. You may be able to recover the majority of rows in this table, but count on losing some. If you have a sequential number as the primary key then the chances are you will be OK. Create a temporary file, say "FOO". Write some BASIC code that will read the rows in the broken table ("BROKE") using a loop (FORBROKE"), or copy the REVnnnn.* at DOS level. If your primary key is not a sequential number, see if you can do a SELECT on the table (run rlist "SELECT BROKE"). If the select comes back with no errors, write a program as above, but using readnext after the select statement to get the rows. If rlist SELECT comes back with errors, try using copy_row (run copy_row "BROKE","*","FOO","*") to get the rows across. Get a rowcount (run get_rowcount tablename) of each table to see ho

w many rows you got. This may also fail if the header is badly damaged though.

Good luck, and keep those backups up-to-date!

View this thread on the forum...