>My reports aren't simple things that come straight from a table, so I always found the DE useless. I also need a "driver" program to compile all the data into the cursor I use for the report.
>
>I've heard people talking about putting the code to generate the report in the report itself. What do you think about this approach? Where's a good place to put the code. Would I then put the tables I use in the DE, or is that just for tables you're printing from?

Tomorrow you'll make another report, similar to this one, and you'll copy the code with the report. Then you'll have it in two places... maintenance nightmare, and very non-OOPissh.

My preference is to have one selection engine (parametrized, if possible) which will do the SQL for several similar reports, and then have the user pick the combination. All run from the same routine, or from the same modal form for picking parameters for reporting. Just a preferrence, though - sometimes I do it otherwise, but really don't like stuffing code into report.