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.

Some other fields most likely have auto-enter values looked up from another file based on a relationship from the field on which the relookup is being done. This ensures that these fields will get filled in with their proper values.

In this situation, it isn't really doing a "re-" lookup. It's just doing the original lookup of data from the other file.

[ May 29, 2001: Message edited by: BobWeaver ]

So, it is looking up records in the other file based on the serial number, and then replacing fields in the newly found record in the other file from the imported record?

Probably.