A command button seems like the right approach. Of course, the check box, being data bound, was associated with a specific record, while a command button would work on whatever record was current, so with the command button they have to select the desired row in the form2 first, and then click the button. That seems a little inconvenient, perhaps.
But here are a couple of tricks you can use. One, you can display the rows in a subform (unlinked) within form2. You can display the subform in form view, but design it to look very similar to a datasheet. That lets you put a little square command button on each row. You could even put a check mark on the button if you want.
Second, you could do the same, but instead of putting a visible command button on the subform detail, put a transparent button on top of the whole row. Then the user can click anywhere on the row to update it. (Caution: This might make it too easy to make mistakes, too!) Note that this isn't appropriate if they can edit any of the fields; if you cover them all with the transparent command button, they won't be able to edit anything. Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein