>Hi Srdjan:
>
>>Update:
>>Saw your form report right now! How does your preview/Print Works ?
>>Can it accept/provides for any scripting? That is the part I am interested foremost. If so then I can enable my tool to output straight there as well. Pls make it open :)
>>
>
>The GDI part uses all the functionality available in the GDI+ classes of the .NET Framework (System::Drawing namespace).
>
>For preview / printing it uses System::Drawing::PreviewPrintController. What is interesting is that we also have an assembly, code compatible with the .NET one, that can output to SVG, PDF, and more. We hope eventually make a VFP class that can output to whatever wants and can be plugged into the pipeline.
>
>It supports scripting in VFP language.
>

That is great news!

Aldough, IMHO you should invest more resources into compiler
aspect and leave reporting elements for later.
What you advertised to do, is HUGE undertaking by all criteria
so you will need all your powers there.

Also (lately) Reporting with VFP is not that bad after all.
There is new VFP9 stuff out there, there are nice 3p tools doing all kinds of cool stuff (XFRX alows scripting for instance) + you hv freaks like myself who do things like this for a sport :)

What you are trying to do (VFP compiler) is IMPORTANT to menu
VFP 'soldiers' out there in cold. Knowing that there can be continuation
of our project lifes in NET, can greatly lift up this community spirit.
And not only that, but also improve our account balances!
Unlike some skeptics here, I do believe that small inspired/dedicated team can do miracles. VFP itself was one of those ventures.

I am sorry, I really misunderstood yr previous message. If you really
meant for me to somehow contribute in your product, then I am honored by that. Hope you did not get ofended in any way. When the right time comes, It will be my great pleasure to contribute / be any part of that story.

Once more, All the best.
Hope you stick arround.