I just read the book "Professional Visual Basic 6.0 Business
Objects", by Rockford Lhotka, and I have a question regarding one
subject that is not covered within the book. The question is:

As I understand from this book, one of the many key points of using
layers (Interface, BO and DB, etc.) is to hide the databases behind
the BO layer, so the user can have the data after is properley
procesed by the business rules of the application. When it comes to
reporting, how can I give the user the ability to create new reports,
or edit existings reports (therefore, make new relations between
tables and calculations not considered in the original design, but
possible using the existing data), without exposing the database
structure? Is there any object model that could let the user access
the data without compromising the BO layer? Or do I have to expose
every possible relation o reporting, deniying the ability to the user
to create new ones?

Thanks in advance.

Jesús Dugarte
Venezuela