You may need to issue SET RELATION to link the cursors. If there is a 1 to many relationship you may need to use SET SKIP as well. Moving the pointer in the many (child) table should not move the record pointer in the one (parent) table until each record in the child table that matches the one record in the parent table has been traversed.
Solution 2:
Use an updateable view to form a single cursor.
Terry Rooks
Software Systems Architect
Microsoft Certified Solution Developer.Net
If at first you don't succeed, then skydiving definitely isn't for you.
