Do you have a solution because "using continuous forms" doesn't sound like it solves your problem. When you have a set of data, the implication is there is a second table involved that controls the set. For example, you might have a batch of payments that all have to be applied or not applied. Because the way bound forms work, this is not directly possible since each record is committed separately from every other record and due to the possibility of user error or system failure, not all records might be entered before the form is closed so you have do do something else. Galaxiom suggested a transaction. That's the right concept but forms already operate within a transaction so the example doesn't do anything that Access isn't already doing and the example uses a continuous form. A continuous form is just like a single form in that it updates ONE record at a time. So, if you are interested in having more detail on the two suggestions I offered, just post back on the one you think might work best for you and I'll go into more detail.
