>Peter is not alone in suspecting other reasons for discontinuation of VFP. I would guess however that the arguments of not releasing a next version will not going to be public in the near future as those involved are still working for MS.

It really doesn't matter what the resons are. The decision was made.

>
>Personally I suspect that since many VFP team members have been working on VB.NET for some time now, they have became very valuable for the development of it, leaving less room to work on a new VFP version.

I think it's the other way around. They moved to other teams because they knew VFP development was winding down.

>Now back to the original point. Peter wants to know the reasoning for stopping the development, making his future decisions. I think he has the right to in asking this.

What difference does it make? Whatever the reason, it won't be reversed. I said it before in another thread. Let's stop wasting our time in this discussion and get on with making great applications for our customers.

>Whether YAG will or can answer that is a different issue. But at least be clear about it. There is no point in beating arround the bush. If you can say, say. If not say so too.

I think it's clear that YAG won't comment anymore on this. He's posted replies in other threads in the past couple of days and has chosen to not respond anymore to this question.

>It would also be interesting to see what the alternatives are from a MS POV. VB.NET ?? Hmmm, I'd thought to see a language closer to VFP to make that recommendation:
>- Better dynamic typing possibilities (rather than strict typed)
>- Better data handling (Possibly with LINQ, though there are doubts)
>- An alternative for VFP scripting (EVALUATE(), &-macro, COMPILE and EXECSCRIPT())
>- A better way to interactively troubleshoot or manipulate data (Command window)

Keep your eye on VB.Net in the next two or three versions. You'll see lots to like and come to think "WOW! This is VFP done better!"

>All in all, they are very different right now.
>
>Maybe it is too early and the .NET platform will provide that in the near future to a reasonable extent. Maybe some other vendors can chime in here.