Can some one please explain what a relookup is looking up and replacing? I have taken over an old script and am trying to figure out what he was trying to do. For an import script, he did a show all and delete all records. Then he imports some records and goes to a layout. Fine so far. Then he does a Relookup on one of the fields. Why? It is an access number common to all the files but he hasn't accessed any of them. Shouldn't there be a lookup first? Then he goes through a series of perform scripts, all of which I understand, does a sort, goes to another layout and prints the report. Then he does another perform script which goes to yet another layout, shows all records and does a Relookup on another field, the serial number. No lookup before hand, so I am not sure what it is he is relooking up and replacing. I've researched five text books and none of them explain it very well.

Before the relookup script step there should be a Go to Field() step. The relookup refreshes the values in some fields defined to depend upon the field specified in the Go to Field() step. First look for a relationship based upon the field in the Go to Field() script step. Then look in Define Fields for fields with the characteristic "lookup" and see if they use this relationship. For instance, you might use a lookup to use a zip code to "lookup" a city and state in a file with city/state matched with zip code.

-bd