>Not sure I'm following you here...

Thinking about it, my core problem is being able to change the data the user sees, without having to Save() and Requery() so they can undo. Not just in this specific case, but throughout the app. :/

>Are you saying that if the user answers appropriately, you will delete ~60 records from your table, and then you want to display a new set of ~60 records instead? Or are you saying you just want to display a different set of records?

The first. The specific case is recording attendance when the class schedule is changed. I have to remove the original attendance and create a new set. There's no guarantee that the new schedule is going to be equal to the previous one.

>Have you thought about filtering your view dynamically? That way, you can change the display without having to go to the back-end and retrieve data. This would be advisable if users can make fast/furious data intensive changes, which is what I think you're talking about?

Not sure filtering would work. It's already a parameterized view, and due to the setup, the field that needs changing is the view parameter.