testing for corruption

[Jeff Harrison]

--- Nancy Palmquist <nlp at vss3.com> wrote:

> Scott Nelson wrote:

> > We had a file get corrupted while changing the
[...snip]

> > 
> Scott,
> 
> You really can not fix this by running anything
> directly on the file itself.  In 

[snip]

I wonder if there would be any demand for a filepro
corruption detector (written in filepro of course). 
This routine would just prompt the user for the name
of the filepro file to check (or it could be passed on
the command line) and it could output the record
numbers where corruption appears, and perhaps a
description as to what kind of corruption it is.

It would internally use the alien file technique to
analyze the data.  I don't think this would be too
difficult to develop at all.  Any thoughts from this
list?  Would this be a useful tool to have in the
toolbox?

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The fastest and
easiest ways to generate filepro exports and imports.


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs