Enjoy and please do ask <s>.

Look: there are sweeping underlying changes in the product, involving the use of GDI+ rather than GDI, the opening up of the Preview API, and quite a few things more.

The idea from the start was that you should be able to take advantage of these changes *without* writing new reports (or writing report listeners!).

ReportListeners expose an object interface into those changes so that, if you want to do *more*, you have the tools.

FWIW I really do not believe that "wanting to do more" vs "not wanting to do more" has anything to do with relative smarts.

You have motivations and incentives and investments in one direction, somebody else has them in another direction.

That's how things appear at the beginning. And then some other requirement comes along, and you (each) have different incentives, and you (each) realize it's not a 0-1 decision.

And VFP offers (both of) you what you need, when you need that approach.

That's the theory anyway. Not so much what happened when 2.x SCXs became 3.0 SCXs. Much more like when we got the ability to access remote data sources, but kept our DBFs (and, for those who care, because I still don't <g>, got DBCs). Meanwhile, our native-SQL got more sophisticated, even for the DBFs... and our ways of thinking about data got enriched too, even when we were using DBFs.

Not a 0-1 decision but an application-by-application choice, sometimes even mixed within an application.

An enabling thing. Not a thing you are forced to do.

>L<