Windows XP revisited

[Bob Stockler]

Walter Vaughan wrote (on Thu, Apr 28, 2005 at 08:58:54AM -0400):

| 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 agree with everything Walter wrote except that I would make
the Alien file's map have the 20-char first field, but then
followed by each of the fields in the "real" map file.  Then
I would put as many of the fields (except maybe field 1) on the
screen (perhaps letting filePro create screen.0 would do it -
I'd make the field names in the map be F1, F2, F3, etc., so
they wouldn't take up too much room on the screen).

One or more of your fields has a lenght that consists of too many
or too few characters (I couldn't read your representation of the
screen shots of where the alignment looked OK and where it didn't).

In dclerk, going back and forth between an OK record and the next
one should show you right away if the record length as defined in
the map is too long or too short to match the data in the key file.

Having all the fields on the screen should help finding the field(s)
that are at fault as you modify the map of the Alien file.

Bob

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).