Scott,

Interesting Indeed.

First, is it safe to say that there are no 1:M or other complicating factors at work? Hate to even think of doing this with 1:M <s>.

1. start with clean form, no records in the view.
2. The "Save" button is disabled
3. User clicks "New" button. Record is appended, "new" is recaptioned as "Repeat" or something like that
4. User enters first record.
5. User clicks on "Repeat" (the recaptioned "new" button). This is then disabled, and "Save" is enabled
6. When user clicks "save", pull the data from record #1 into a cursor
7. Go field for field between view (on record 2) and cursor (which is record 1)
8a. You could then display a list of differing fields, or, better yet...
8b. ...Run the fields down the form, so that you can suddenly make visible a second column of fields containing the values from record 1 (with some color clue to the differing fields)
9. When user has satisfied requirements that records match, delete record 1 and commit the changes (which commits record 2).
10. Reset everything so that you are back at step one.

The only problem I can see is that it will get silly when the user has entered differing values. What if some values from record 1 are OK but other values from record 2 are the right ones? How does the user change some in record 1 and some in record 2 without going crazy? Perhaps you could beg the boss to let the user change only record 2, or you could use that columns idea in 8b to force the user to make both columns match.

Hope this helps.