testing for corruption

[Jeff Harrison]

--- Fairlight <fairlite at fairlite.com> wrote:

> Only Bob Stockler would say something like:
> > Jeff Harrison wrote (on Mon, Feb 04, 2008 at
> 11:01:16AM -0800):
> > [snip]
> > 
> > | I wonder if there would be any demand for a
> filepro
> > | corruption detector (written in filepro of
> course). 
[snip]

> Define "corruption" in this context.
> 
> Record 20-byte header at wrong/unexpected offset? 
> Possibly detectable,
> since they'd be outside the printable character
> range.
>
Good point.  I had defined corruption (for myself) as
any non-ascii characters that are stored in real
fields as specified in the map - that is the
corruption that I really care about.  Also, if data
exists in deleted records - I would call that
corruption.

Also good point - I see no reason that this could not
be extended to check and make sure that the system
maintained fields are valid (ascii/valid dates/or
blak) as well - as an option.  I suppose we could also
extend it to optionally let you know if it passes the
field edits. 

This is all most people care about isn't it?  I would
want to keep this very simple at its basic level, then
people could then use flags for options to do the more
detailed validity checking.
 

> Further...when you find such a misalignment, what is
> the procedure for
> continuing reporting?  Reset the record start offset
> to where you -think-
> the record actually starts?  Continue onwards as if
> nothing happened,
> assuming the other offsets should be correct? 

Yes.  Continue on.  Lets not make this too complex
-yet.  There would need to be another utility to
actually fix the problem(s) - or you just need to fix
it the old fashoned way - then run this utility again
to see if you are clean.
[snip]

> And technically speaking, both those scenarios are
> actually the least
> likely form of corruption unless you're physically
> losing a drive's
> integrity.

[snip]

I don't care what the cause the of corruption is - I
keep seeing people ask this list how they can check
for invalid data in fields - this would fit the bill
for that, I think.

[snip] 

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to import and export with filepro. 


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping