Ben,
would you explain a little bit the idea of "wrapper" business object?The BusinessObject = 1 table is slightly problematic in the case when you would need to create a object that would include columns from several tables (a SQL join) and perhaps some computed fields (some computation rather done in the database than in the application).
In a Oracle environment would DDT bring any help on this issue?
Lastly, is this true: the data structure of the business object is just a place holder and the query populating the data structure can be whatever, e.g any SQL-statement?
Kari