>Fabian,
>
>>I have a architecture question in my mind, usually business objects deal with data that is related to a particular table or set of tables, but usually when a report is printed most likely OLAP or Denormalized tables are accessed, so there is not business logic applied to the data, I don't think accessing the data directly from the form would be smart, I also think that reusing the functionality of the data adapters is smart, so how do I call my stored procedure to get my data for a report.
>>
>>Theoretically I would like to have a form call a report object, the report object will call the stored procedure, prepare the report and send it back the the UI so it is displayed. In the MM world, I can see this object been a custom access object, any suggestions or ideas?
>
>Although you COULD use a data access object directly, I recommend creating a report object instead that uses a data access object. This allows you to vary the back end in the future since the business object loads the appropriate data access object dynamically at run time based on the specified data source. You can then call one of the ExecSproc commands to execute your stored procedure.
>
>Regards,

Kevin, I'm guessing you are using a business object as a report object, I have to give it a try to see how it works, so far I like the framework, I feel this version is much better than the VFP. Personally I think this is due to the language features in .NET.


Thanks Kevin
Fabian