Corrupted keybackup

[Jeff Harrison]

----- Original Message ----

> From: Richard Kreiss <rkreiss at gccconsulting.net>
> To: filepro-list at lists.celestial.com
> Sent: Fri, June 10, 2011 4:13:30 PM
> Subject: Corrupted keybackup
> 
> I added 2 fields to the end of a file. One zero length and the other  5,.0.
> 
> Some of the records are ok and some are corrupted.  It appears  that most of
> the bad records are in the middle of the file.
> 
> Any  backups they may have had from the time the fields were added are  now
> gone.  The primary key is ok. 

What do you mean by "The primary key is ok."?  Do you mean you have multiple key 
segments (extents or qualifiers)?

> On a monthly basis, the order  details are
> posted to the history file.  

I'm not sure what this has do do with anything - does this have any significance 
as to your data corruption?

> This is this and the backup are  the ones that
> are bad.
> 

Huh?  

[snip]
> 
> When I looked as  some of the records while stepping through the file by
> record number, I noted  that many of them had no creation date.  As such, the
> filePro may be  looking at these as blank records.
> 

I think you mean to say that filepro may be looking at these as deleted 
records?  I believe that filepro uses the first byte in the 20 byte header as 
the deleted record flag, not the creation date.

> Any suggestion as to how I can  straighten this out will be greatly
> appreciated.
> 
>   

I suggest that you get the corrupted key file and map to someone that has dealt 
with this type of thing before.  They should be able to clean it up.  It would 
be very involved to tell you how to do this.  Also there are many variables 
depending on the nature of the corruption.

Good Luck.

Jeff Harrison
jeffaharrison at yahoo.com
Author of JHExport and JHImport