Ok, that's the how. What about the "should I?" It seems good in that the report is encapsulated, but loading a whole problem in one of the DE methods (probably AfterOpenTables?) seems wrong somehow. I know there's really not a "wrong" way to do things, but there are better and worse ways. I don't want to start a habit that will be frowned upon buy future bosses.

Thanks,

-Michelle

>Hi Michelle ---
>
>I maintain an application (I didn't write it) where the setup screen and other code resides in (ta da!) DataEnvironment methods. I see no other way to do it integral to the report itself.
>
>
>>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?
>>
>>So many questions, so little time... :)
>>
>>-Michelle