Hi Arto,
I'm happy to say that I'm actively working on Version 2.5 currently. The big items of improvement are XP Debugging, PDF printing, better ASP.NET support, and a lot of other stuff including your contributions.
This is why I like vfp. It's challenging and fun to do these types of projects in vfp and I think it's easier to make a contribution here since our numbers are not as large as the .NET/VB masses where everybody is working on the same thing.
I'm very happy with the interop opportunities of making vfp work with .NET and other MS technologies and hopefully this will continue in the future. I think we have VB6 to thank for this since there is so much legacy VB code that will have to be supported going forward. I just wish MS would promote VFP strengths more. When these apis between vfp and the newer stuff stop is when I'll start to worry.
>Hi Claude
>
>Any news for the update?
>
>BTW You have been a VFP guy as fara as I'v followed these threads, so here are some tought of mine:
>
>It seems that time to time there is a tidal of "les miserables" complaining of Foxpro versus "when, why, why not, NET, Access, VB (or even to itself, figure it out) etc..." Still from the earliest version of Fox usage I'm still happy with it. There is almost nothing I can do with it (tell me what can't be done and somenone shows how it can be done, or what do you think?). Another story is the MS investments of VFP marketing every now and then I hope and beg that it is not leaved only (almost) on the shoulders of developers but on the other hand I dont see any hazard to the customer for using VFP (but regret to say that sometimes it's better to be "amorphous" when telling what is the used tool) and then on the other hand you have not to be so amorphous if it is marketed better!
>
>AT