Ed, I am probably missing something and most likely don't see the bigger picture, but I still have some questions regarding this issue.
>From what I understand...at least the way we are setting things up, we are instantiating the bizobj as an object on the form and working with it there. Any other forms that we may open may be using the same class for the bizobj, but they are different instances of the bizobj, so any data updates to the bizobj would be independent of the other forms. In this case, my example of the don't care situation comes up, that is...if the user confirms that they want to cancel, then the form should just go away with no "undoing" needed. With that said, one of your responses was, if I understood it correctly, that we need to explicitly reverse any changes made to the bizobj before closing the form because the bizobj may be referenced on other forms. So my questions are... 1) If there is a reference to a bizobj on another other form and it was instantiated on the form that we are trying to close, wouldn't it break the other form when the reference to it goes away? 2) If the bizobj was passed to the form we are trying to close as a reference from another obj (i.e. form), should closing the form undo any changes to the bizobj eventhough changes to the bizobj may have been made on the bizobj's parent form (i.e. not the one we are trying to close)? My point here being, the bizobj does not know where the changes come from, so is it correct to force undoing any changes? Much appreciated, Larry _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/!~!uenerkvcmdkaaqacaaaaaaaaaaaaaaaaabgaaaaaaaaaafa2fnyupuomnfpiynbeqckaaaaqaaaa29knsvk1dkqxlo9ny9empqeaa...@charter.net
