Hi Frank,

>>
>>Hi Frank,
>>This is correct. What happens when you choose to save is the Business object Raises an event. The controls that are bound, will save their changed values back into the entity, then the save finishes. That is why if you just move off the form or navigate away without the save, the values will not be "bound back" to the entities.
>>Tim
>
>Thanks, I had stepped through the MM code to see what was happening and discovered that (if I understand it correctly it occurs in mmBusinessObject.CallStateChange). Can I raise this event manually? Or do I have to manually update the DataSet with my values, then save the dataset in a session variable. If so, this looks like it's so much of a pain I might go back to doing winforms applications. :(


You can manually raise the state change, check out the Dev Guide under Advanced Topics. I bet there isn't that many times you need to save temporary data while you leave the page, but it isn't that hard to architect that if you know that is your need. The bind back or two way binding that MM offers is great but you do have to figure out how it works to have a handle on it. Once you get the hang of the ASP stuff it isn't that bad. The worse part I find is laying out the form since using floats takes the objects out of the document flow and trying to always keep things where I want but yet still not hard coded. I spend more time doing that then anything else.

Win forms doesn't have any of these problems but your users have to all install the application. My focus right now is WPF with WCF data access and hopefully OnceClick for the installation. I really like the richer user interfaces and think the users do also.
Good luck
Tim