C# / SQL Server 2005 Should I use OOP for reports and datagrids?
===

My Web Application is separated into different layers, one of them is the business layer that works like this:

    PersonBusiness pb = new PersonBusiness();
    Person p = pb.GetPerson(10);

and then I load the person object into ASP.NET controls whenever viewing records, and then for saving I do something like this:

    PersonBusiness pb = new PersonBusiness();
    Person p = new Person();
    p.Name = "Alex";
    pb.SavePerson(p);

What if I need to display a report within the app that is actually the result of calling a view from the database that is actually a mix of different objects in the business layer ?. Do you recommend just bypassing the business layer and loading the dataset that comes from the view ? Does it make sense to use OOP here ? If true then I would have to create a custom Object that would only be used for that  single report and nothing else.

This is more of a generic question that does not strictly apply to C# and SQL , but applies basically to any business application out there...

I hope my question makes sense, 

thanks for your time and have an nice day   
