Have you considered implementing a publisher/subscriber pattern in the framework? For example, in your sample application I would like the Order Entry form to be able to subscribe to a customer change on the Customer Maintenance form that would allow the Order Entry form to update itself to reflect that change.

The framework doesn't have that pre-plumbed, but we engineered all of the hooks to be event-based rather than method overloads, so you can attach to them from anywhere rather than only within the business objects. So, your OrderEntry business object could attach to an event on the CustomerMaintenance form or to a business object on the CustomerMaintenance form and should be able to achieve exactly what you're after.