This thrills me!. Did you see the Printing sample we shipped in .NET Extender, this is the starting piece of what we'll build for Reporting.

It is basically a Report designed on a form with full oop. Every Control placed has its method GenerateOutput, InitPen, InitBrush, and more. This is We think an OOP Report should be.

Are you telling me you have something in the same venue that our Reporting Draft?, but far more advanced. This sounds to me like a Nice Business to make with you.

So you also need the GUI part?, that is what just I told to Thomas Ganss, the GUI seems to be a Top Priority for the programmers.



>>
>>We already implemented some obvious wishes:
>
>>2. A true OOP Report based in the Form paradigm.
>
>Interesting!
>FYI, I have been working on a reporting tool (freeware) for a quiet a while now, that among other features, includes fully OOP, multilevel grouped reports. (form controls are just one of OOP report implementations)
>
>It is nice to know that whole project can have life after VFP life, (since you are building VFP compiler for .net) and also that there are other
>people who believe that reporting can be much more (or much less!) then
>what comes out of VFP box.
>
>Looking fwd to your product!
>
>
>