Thanks, Rick; I expected there wouldn't be quick answers.

Your post does highlight the primary issues involved.

When you mention a "good business object framework" then mention that the "application specific" part is primarily reporting, do you mean that "good business object framework" could be non-application specific, but to be Database specific instead? Or could it be general enough for any database, any application?

Where would one start in designing/obtaining a good BO framework?

>There are no quick answers to this,
>
>A good business object framework will have standard methods for doing common things like retrieving records, updating, saving and deleting data so all that's left is to do application sopecifc SQL for reports etc.