Windows XP revisited

[Walter Vaughan]

Luke Jenner wrote:
>>>map:460:0:18:77d55221:M at Y8"J`z8<pEYcM!

Not to beat this dead horse anymore....

Your map doesn't match your key

If your key is not busted since you said it looks good every 60 records.

*I* would create an "Alien" filePro file that would have pointed to the 
key file in your table just to look at the file and see how what is off.
Of course do not in any circumstance allow filePro to rebuild the file.

I'd start off with a file that had
field 1) Binary Header	- 20 characters
field 2) Key   - 460 characters

filePro will complain about creating a screen with that big a field, but 
just put *1 on line one and *2 on line two of the screen.

What you'd expect to see is binary data in the header and clean data
I'll expect that you'll see binary data move location as you move from 
record to record. Increase or decrease the size of the key section in 
your alien file until everything stays in place.

Since you said that every 60 records everything looks fine, and you have 
  essentially 480 characters per record in the key segment, I'd change 
the key first by seven in the alien file.

You will find that the map currently is wrong. Fixing it is just a 
matter of time and materials.

I've probably taken more time to write this message than it would take 
to find/fix/finish the problem.