I would like to in the event of a suddenly damaged table be able to post the data to an alternate table.  the problem is that I would also like to intentionally damage a table (in a way it can be repaired) so that I can test my procedures.

Any ideas?

Thanks, John

John Taylor wrote:

I would like to in the event of a suddenly damaged table be able to post the data to an alternate table.  the problem is that I would also like to intentionally damage a table (in a way it can be repaired) so that I can test my procedures.

The problem I typically see is 'header corrupt'

Any ideas?

Thanks, John

John


I remember asking a similar question - to corrupt your table get a hex editor and attack the .dat file - if you get it just right the table will still open but be corrupted, if you don't it won't open.

The latter is the most probable outcome.

I don't think Tim is overly keen on distributing instructions on how to intentionally corrupt DBISAM (or ElevateDB) table - can't think why


Roy Lambert

Roy Lambert wrote:

John


I remember asking a similar question - to corrupt your table get a hex editor and attack the .dat file - if you get it just right the table will still open but be corrupted, if you don't it won't open.

The latter is the most probable outcome.

I don't think Tim is overly keen on distributing instructions on how to intentionally corrupt DBISAM (or ElevateDB) table - can't think why


Roy Lambert

Perhaps I should submit a support ticket, maybe he will tell me privately via emai

John

John


A better way is to ask your users for a corrupted table before they repair it - might have to wait a while though

Roy Lambert

John,

<< I would like to in the event of a suddenly damaged table be able to post the data to an alternate table.  the problem is that I would also like to intentionally damage a table (in a way it can be repaired) so that I can test my procedures. >>

The easiest way is to just write some junk to the middle of the .idx file.  That will trigger a repair without getting too far into the weeds of dealing with what is "normal" corruption vs. what is "unrecoverable" corruption.  It is fairly easy to cause "unrecoverable" corruption by simply writing junk to the .dat header.

Tim Young
Elevate Software
www.elevatesoft.com