I always like to make sweeping claims like this as there is always someone (or somebodies) that know more than I do and can provide additional information that makes the tutorial even better. 

• Dynamically configuring a report based upon an SQL Server table (ReportEngine)
• Methodology for abstracting business objects (three layers are illustrated)
• Class Diagrams for Business Layer, BOL and Report BO classes
• Description of the Business Binding Source as it relates to Generics
• Creating a simple Customer List
• Filtering the contents of that Customer List by collecting information from the user
• Adding custom properties to Report Business Objects
• Illustrating how powerful the Report Engine table can be
• How to subclass an XtraReport so that common processing can be consumed over every report in your application
• Creating an Inherited Report
• Create a Master-Detail using the data "Flattening" methodology
• Create a Master-Detail report by using multiple Data Sources and Sub-reports

Here it is ... https://www.dropbox.com/s/1e82qqb7h96pfu6/DXStrataFlix.zip

DevExpress 13.2.7

Free, web based, UML Modeling tool (FREE)

Charles T. Blankenship
Senior Consultant
Novant Consulting, Inc.
704.975.7152
http://www.novantconsulting.com

Hi Terry,



I use both.  Mostly views, I tend to prepare the SQL statement as close as needed by the report, or as generic as possible to be re-used with more than one report.  The rule for me to use Custom Field Properties is if the data to be shown in the report is just couple of hundred records, then CFP performance should not be a problem, but if the report may output more than 500 records, then I create a virtual column in my SQL statement (view) to have the data there.

That is one of the main reason the SF builder would give you the option to create a BO for the report

Edhy Rijo