>Yes I could. But I'd have to call BindControlToData() on every control on the form. There is already an elegant "OOPy" state change mechanism in place. It would be nice to call it with a state change causing it to redo the forward binding. I see state change members like "mmBusinessState.Retrieved" that have no implementation. The finished app will have hundreds of forms, so I need to find the cleanest solutions possible.

Honestly, if you're just attempting to handle a "Cancel", I would personally just build a button that navigated to the initial form w/record that the user would have navigated to, to edit the record in the first place. It's simple (which I always like), and should work just fine. It also doesn't require any redirects, so you're not generating any unnecessary network traffic.