Data-aware Forms versus References to Custom Collections and Broadcastersgreenspun.com : LUSENET : OCI Best Practices : One Thread
Data-aware Forms versus References to Custom Collections and Broadcasters
OCI Enterprise business objects and user-interfaces implement two style of architecture.
- Data-aware forms which directly reference the TDataSet result sets in their business objects
- Non-data aware forms which "listen" to changes to business object properties
Whenever possible you should use data-aware forms. The advantages of the data-aware approach are:
- No need to code event listeners -- the data-aware controls automatically reflect changes in data
- No need to use our custom collections and collection items because "cached updates" cache changes
- Uses standard, well-documented, Delphi components and events rather than custom components
The limitations of the data-aware approach are
- Your user-interface choices are limited to controls on the "Data Controls" tab of Delphi
- Requires database field-specific programming, rather than object property-specific programming (which is only a problem when the data model does not jibe with the object model)
For an example of the data-aware approach see the Producer system. For am example of the custom approach see the Legal System.
-- Anonymous, January 24, 2000