>>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.
>>
>Michelle,
>
>What's wrong with just putting procedural code in the method that calls the report? That's the way we did it for years before OOP -- and there is nothing about the VFP report that even remotely suggests that it was designed for an OOP environment.
>
>Undoubtedly what you are doing is creating a cursor in the method code, loading it with SELECT, and preforming routines that load summary data into some of the cursor fields.
>
>T'ain't wrong at all -- and this he new fangled stuff of putting it in a data environment just gives me a headache.
>
>regards,


That's what I'm doing now. I just wondered if there was a better way.

Thanks,

-Michelle