>George and others,
>
>I can't help myself but by becoming too emotional to certain extent. Sorry for the whining and I know that there is no permanent on this earth not even our life. If it's the beginning of the End (VFP) then I so be it.
>
>I think that RESISTANCE is FUTILE at this time...

Sorry to take so long to reply back, Jess. I wanted to give this my full consideration.

Both JimB and JVP have told you that VFP isn't dead. I agree with them. However, I'm going to say something that no one else has, unfortunately, pointed out.

A lot of the FUD about this, IMO, is based on the concept that "the desktop is dead". I don't agree, and I don't agree for a number of reasons.

First, some applicaations, particularly those that do a lot of data munging, probably shouldn't be moved to a browser/intranet based solution. While it, again IMO, will happen that these applications are attempted to be moved there, it really isn't in the best interest of either the company or, and more importantly, the individual user.

The prudent developer should be able to recognize when a browser/intranet based application is applicable and when it isn't. Further, they should be well versed enough to articulate the reasons. Those that do will be doing a service to their empolyer and their users. Those that don't, well, eventually they'll be out of the loop.

Second, the reason that PCs became so prevelant was because it put power in the hands of the user. Many IT departments were either unwilling or unable to respond to the needs of the users. This led to an, "Well, I'll do it myself" attitdue. Placing every application on a browser based/intranet based solution ultimately returns us to the days of "Big Iron" and takes the power out of the hand of the people. Certainly, this is not to say that there shouldn't be these types of applications, but it does point to the fact that, ultimately, history will repeat itself and the trend will cycle back to client side applications.

Third, and perhaps the most compelling, is that browser based/intranet applications can never be as productive (in terms of performance and usability) as client side applications.

Given these reasons, there is no reason to think that VFP won't be a "player" for many years to come. It does, however, require that those of us who develop in it be objective and use the right tool when necessary.

>Difficulties in learning a new language is just a secondary factor to us programmers. It's the availability of time. In a developing countries like us, we don't have our own computers at home. We rely on computers in the office. And while in the office, we stick to project completions. Well, it's not the fault of MS, it's the fault of our economy. :)))))

Jess, I both understand and sympathize. I've personally been in a such position. However, this is business and this isn't personal. Microsoft isn't in business to be a charitable organzation to meet the needs of every developer, everywhere. They're not in business to make friends or influence people. In fact, they're not even in business to make software. Like all other companies, including your's and mine, they're in business to make money, pure and simple. When people say things like, "...well, they can so why don't they?" they overlook the this. And that's what's going on.

Creating a VFP.Net isn't a profitable (from my view) proposition. Since it isn't such, there won't be one.

>Good Luck to all!

And to you,