>Two possible ways ( I'm sure there are others ) to do this I can think of. One would be to use the SET SKIP command to set up a one-to-many relationship between table2 and table3 and iterate through table1. I believe properly set up realtions and SET SKIP should iterat through all related records in the child tables before changing records in the top-level table. But, honestly I have not tested this with your scenario or with the SCAN command. If you try this, please let me know if it works properly. If I get soem time, I will try it myself.
>

I just tested this and it seems to accomplish what you want. A sample of this is given in the Help under SET SKIP.

Bill